Triple

T35227473
Position Surface form Disambiguated ID Type / Status
Subject Vosges passes network E1017136 entity
Predicate hasPart P35 FINISHED
Object Col du Donon
Col du Donon is a mountain pass in the Vosges Mountains of northeastern France, known for its strategic location, scenic routes, and nearby historical and archaeological sites.
E2134638 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: Col du Donon | Statement: [Vosges passes network, hasPart, Col du Donon]
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: Col du Donon
Triple: [Vosges passes network, hasPart, Col du Donon]
Generated description
Col du Donon is a mountain pass in the Vosges Mountains of northeastern France, known for its strategic location, scenic routes, and nearby historical and archaeological sites.

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_69f76de12e4c8190bc46b71a32858356 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78eab16888190bffc8a61abec7490 completed May 3, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3819d027988190b9236a1405f32483 completed June 21, 2026, 5:05 p.m.
NEDg Description generation batch_6a381a4b79988190a061802a0e60c8cf completed June 21, 2026, 5:07 p.m.
NED2 Entity disambiguation (via description) batch_6a381ac54dcc81908fd17039e9486663 completed June 21, 2026, 5:09 p.m.
Created at: May 3, 2026, 4:02 p.m.