Triple

T30526243
Position Surface form Disambiguated ID Type / Status
Subject Lagny-sur-Marne E776851 entity
Predicate intercommunality P15149 FINISHED
Object Marne et Gondoire
Marne et Gondoire is a French intercommunal structure in the Seine-et-Marne department that groups together several neighboring communes for shared local administration and services.
E1920753 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Marne et Gondoire | Statement: [Lagny-sur-Marne, intercommunality, Marne et Gondoire]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Marne et Gondoire
Triple: [Lagny-sur-Marne, intercommunality, Marne et Gondoire]
Generated description
Marne et Gondoire is a French intercommunal structure in the Seine-et-Marne department that groups together several neighboring communes for shared local administration and services.

Provenance (5 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69f2249c11508190ae7e955755ccfb01 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6880f92d48190a6ac8547c34ef7d3 completed May 2, 2026, 11:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2856ed03ec8190bc5c173af116d27d completed June 9, 2026, 6:09 p.m.
NEDg Description generation batch_6a2857b589ec81909e258772b91e5954 completed June 9, 2026, 6:13 p.m.
NED2 Entity disambiguation (via description) batch_6a285832e13c8190b4156a62e3a56c30 completed June 9, 2026, 6:15 p.m.
Created at: April 29, 2026, 8:17 p.m.