Triple

T27146508
Position Surface form Disambiguated ID Type / Status
Subject Tergnier E681961 entity
Predicate servedByRailwayLine P848 FINISHED
Object Amiens–Laon railway
The Amiens–Laon railway is a regional rail line in northern France that connects the cities of Amiens and Laon, passing through key intermediate towns such as Tergnier.
E1773160 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: Amiens–Laon railway | Statement: [Tergnier, servedByRailwayLine, Amiens–Laon railway]
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: Amiens–Laon railway
Triple: [Tergnier, servedByRailwayLine, Amiens–Laon railway]
Generated description
The Amiens–Laon railway is a regional rail line in northern France that connects the cities of Amiens and Laon, passing through key intermediate towns such as Tergnier.

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_69eefacca3888190b67238d380e8f28b completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f624c59988819084bf9be39c3fa44b completed May 2, 2026, 4:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12b220cef88190aa6ed453692e3064 completed May 24, 2026, 8:09 a.m.
NEDg Description generation batch_6a12b336f16881908177da118f0043a5 completed May 24, 2026, 8:13 a.m.
NED2 Entity disambiguation (via description) batch_6a12b39083908190b689245002e150c7 completed May 24, 2026, 8:15 a.m.
Created at: April 27, 2026, 9:11 a.m.