@@ -75,17 +75,22 @@ For simplicity, one can use one of the preconfigured pipelines:
7575
7676.. code-block :: python
7777
78- from renard.pipeline.preconfigured import bert_pipeline
78+ from renard.pipeline.preconfigured import co_occurence_pipeline
7979
8080 with open (" ./my_doc.txt" ) as f:
8181 text = f.read()
8282
83- pipeline = bert_pipeline(
84- graph_extractor_kwargs = {" co_occurrences_dist" : (1 , " sentences" )}
85- )
83+ pipeline = co_occurrence_pipeline()
8684 out = pipeline(text)
8785
8886
87+ The following preconfigured pipelines are available:
88+
89+ - :func: `.co_occurrence_pipeline `
90+ - :func: `.conversational_pipeline `
91+ - :func: `.relational_pipeline `
92+
93+
8994Pipeline Output: the Pipeline State
9095===================================
9196
@@ -137,7 +142,7 @@ Tokenization
137142Tokenization is the task of cutting text in *tokens *. It is usually
138143the first task to apply to a text. 2 tokenizer are available:
139144
140- - :class: `.NLTKTokenizer `
145+ - :class: `.NLTKTokenizer ` is the tokenizer from NLTK.
141146- :class: `.StanfordCoreNLPPipeline ` does contain a tokenizer as part
142147 of its full NLP pipeline.
143148
@@ -148,16 +153,19 @@ Named Entity Recognition
148153Named entity recognition (NER) detects entities occurences in the
149154text. 3 modules are available:
150155
151- - :class: `.NLTKNamedEntityRecognizer `
152- - :class: `.BertNamedEntityRecognizer `
156+ - :class: `.NLTKNamedEntityRecognizer ` is a lightweight NER module from
157+ NLTK, based on POS tagging and rules.
158+ - :class: `.BertNamedEntityRecognizer ` is a NER module employing a
159+ finetuned BERT model.
153160- :class: `.StanfordCoreNLPPipeline ` contains a NER model as part of
154161 its full NLP pipeline.
155162
156163
157164Coreference Resolution
158165----------------------
159166
160- - :class: `.SpacyCorefereeCoreferenceResolver `
167+ - :class: `.SpacyCorefereeCoreferenceResolver ` uses the spacy coreferee
168+ module.
161169- :class: `.BertCoreferenceResolver `, using the Tibert library.
162170- :class: `.StanfordCoreNLPPipeline ` can execute a coreference
163171 resolution model as part of its pipeline.
@@ -166,14 +174,14 @@ Coreference Resolution
166174Quote Detection
167175---------------
168176
169- - :class: `.QuoteDetector `
177+ - :class: `.QuoteDetector ` detect quotes using simple logic.
170178
171179
172180Sentiment Analysis
173181------------------
174182
175183- :class: `.NLTKSentimentAnalyzer ` leverages NLTK's Vader for sentiment
176- analysis
184+ analysis.
177185
178186
179187Characters Extraction
@@ -183,21 +191,36 @@ Characters extraction (or alias resolution) extract characters from
183191occurences detected using NER. This is done by assigning each mention
184192to a unique character.
185193
186- - :class: `.NaiveCharacterUnifier `
187- - :class: `.GraphRulesCharacterUnifier `
194+ - :class: `.NaiveCharacterUnifier ` assigns each mention with a unique
195+ form to a character.
196+ - :class: `.GraphRulesCharacterUnifier ` uses a set of rules to assign
197+ each mention to a character.
198+
199+
200+ Relation Extraction
201+ -------------------
202+
203+ - :class: `.GenerativeRelationExtractor ` is currently in development
204+ and should not be used.
188205
189206
190207Speaker Attribution
191208-------------------
192209
193- - :class: `.BertSpeakerDetector `
210+ - :class: `.BertSpeakerDetector ` detects speaker using a finetuned BERT
211+ model.
194212
195213
196214Graph Extraction
197215----------------
198216
199- - :class: `.CoOccurrencesGraphExtractor `
200- - :class: `.ConversationalGraphExtractor `
217+ - :class: `.CoOccurrencesGraphExtractor ` extracts a graph of
218+ co-occurrence between characters.
219+ - :class: `.ConversationalGraphExtractor ` extracts a conversational
220+ graph: either conversation between characters, or of character
221+ mentions.
222+ - :class: `.RelationalGraphExtractor ` extracts a relational graph,
223+ where the relation between each character is typed.
201224
202225
203226Dynamic Graphs
@@ -240,8 +263,9 @@ When executing the above block of code, the output attribute
240263>>> out.character_network
241264[<networkx.classes.graph.Graph object at 0x7fd9e9115900>]
242265
243- See :class: `.CoOccurrencesGraphExtractor ` for more details on the
244- usage of the ``dynamic `` and ``dynamic_window `` arguments.
266+ Both :class: `.CoOccurrencesGraphExtractor ` and
267+ :class: `.ConversationalGraphExtractor ` support dynamic networks. See
268+ their documentation for more details.
245269
246270Plot and export functions work as one would expect
247271intuitively. :meth: `.PipelineState.plot_graph ` allow to visualize the
@@ -255,10 +279,9 @@ dynamic graph to the Gephi format.
255279Custom Segmentation
256280-------------------
257281
258- The ``dynamic_window `` parameter of
259- :class: `.CoOccurencesGraphExtractor ` determines the segmentation of
260- the dynamic networks, in number of interactions. In the example above,
261- a new graph will be created for each 20 interactions.
282+ The ``dynamic_window `` parameter determines the segmentation of the
283+ dynamic networks, in number of interactions. In the example above, a
284+ new graph will be created for each 20 interactions.
262285
263286While one can rely on the arguments of the graph extractor of the
264287pipeline to determine the dynamic window, Renard allows to specify a
0 commit comments