Triple

T36871957
Position Surface form Disambiguated ID Type / Status
Subject Truyère valley E911246 entity
Predicate hasHydroelectricDam P15311 FINISHED
Object Couesques Dam
Couesques Dam is a hydroelectric dam in southern France that harnesses the Truyère River to generate power as part of the region’s extensive river-dam system.
E2289732 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: Couesques Dam | Statement: [Truyère valley, hasHydroelectricDam, Couesques Dam]
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: Couesques Dam
Triple: [Truyère valley, hasHydroelectricDam, Couesques Dam]
Generated description
Couesques Dam is a hydroelectric dam in southern France that harnesses the Truyère River to generate power as part of the region’s extensive river-dam system.

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_69f76e82339881909607a65c0503d941 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7cff3d97c819087f221ac6e98f35b completed May 3, 2026, 10:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5b649cc28881909e552837d35384d0 completed July 18, 2026, 11:33 a.m.
NEDg Description generation batch_6a5b64fd35348190a3ce8426a9e1db3f completed July 18, 2026, 11:35 a.m.
NED2 Entity disambiguation (via description) batch_6a5b657254fc81909f61c2a9a3922dde completed July 18, 2026, 11:37 a.m.
Created at: May 3, 2026, 4:13 p.m.