Triple

T26899137
Position Surface form Disambiguated ID Type / Status
Subject Weilerswist E677977 entity
Predicate hasRailConnection P848 FINISHED
Object Eifel Railway
The Eifel Railway is a regional rail line in western Germany that runs through the Eifel mountain region, connecting cities such as Cologne and Trier via numerous smaller towns.
E1755624 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: Eifel Railway | Statement: [Weilerswist, hasRailConnection, Eifel 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: Eifel Railway
Triple: [Weilerswist, hasRailConnection, Eifel Railway]
Generated description
The Eifel Railway is a regional rail line in western Germany that runs through the Eifel mountain region, connecting cities such as Cologne and Trier via numerous smaller towns.

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_69eee9befee48190a26f214faa867be7 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61fad18408190a274a3f7022f3104 completed May 2, 2026, 4 p.m.
NED1 Entity disambiguation (via context triple) batch_6a123aa154b88190a3aafd6d26559e1b completed May 23, 2026, 11:39 p.m.
NEDg Description generation batch_6a123bbe49cc81908763b340636d7a60 completed May 23, 2026, 11:43 p.m.
NED2 Entity disambiguation (via description) batch_6a123f9c03f881908e9cc1bc292b3e96 completed May 24, 2026, midnight
Created at: April 27, 2026, 5:49 a.m.