Triple

T25329112
Position Surface form Disambiguated ID Type / Status
Subject arrondissement of Nogent-sur-Marne E635100 entity
Predicate contains P35 FINISHED
Object Bonneuil-sur-Marne
Bonneuil-sur-Marne is a suburban commune in the southeastern outskirts of Paris, France, situated along the Marne River in the Val-de-Marne department.
E2287651 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: Bonneuil-sur-Marne | Statement: [arrondissement of Nogent-sur-Marne, contains, Bonneuil-sur-Marne]
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: Bonneuil-sur-Marne
Triple: [arrondissement of Nogent-sur-Marne, contains, Bonneuil-sur-Marne]
Generated description
Bonneuil-sur-Marne is a suburban commune in the southeastern outskirts of Paris, France, situated along the Marne River in the Val-de-Marne department.

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_69e75a9908108190a95427a97020632a completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f497c2c7b081909a09153061b01fa7 completed May 1, 2026, 12:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5a07872f808190992c70f33bf1ea2c completed July 17, 2026, 10:44 a.m.
NEDg Description generation batch_6a5a0975ef548190905d40a65dcd3fae completed July 17, 2026, 10:52 a.m.
NED2 Entity disambiguation (via description) batch_6a5a0a786e1c8190a4abfcfd3b44a722 completed July 17, 2026, 10:56 a.m.
Created at: April 21, 2026, 1:30 p.m.