Triple

T25043631
Position Surface form Disambiguated ID Type / Status
Subject René-Lévesque E627177 entity
Predicate containsMunicipality P852 FINISHED
Object Pointe-aux-Outardes
Pointe-aux-Outardes is a small coastal municipality in Quebec, Canada, known for its natural landscapes and proximity to the St. Lawrence River.
E1719508 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: Pointe-aux-Outardes | Statement: [René-Lévesque, containsMunicipality, Pointe-aux-Outardes]
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: Pointe-aux-Outardes
Triple: [René-Lévesque, containsMunicipality, Pointe-aux-Outardes]
Generated description
Pointe-aux-Outardes is a small coastal municipality in Quebec, Canada, known for its natural landscapes and proximity to the St. Lawrence River.

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_69e2ff2b4c80819087c916b2b16241b9 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f4530d80148190b959bb48ff7e0c2f completed May 1, 2026, 7:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a118f7614a88190a63b66cb7950032a completed May 23, 2026, 11:28 a.m.
NEDg Description generation batch_6a119053e3b0819092c8e62b5b4ae02a completed May 23, 2026, 11:32 a.m.
NED2 Entity disambiguation (via description) batch_6a1190db5ab48190a5b902fee03abdde completed May 23, 2026, 11:34 a.m.
Created at: April 18, 2026, 6:08 a.m.