Triple
T35345446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Brabant rail network |
E1020726
|
entity |
| Predicate | hasCorridor |
P5520
|
FINISHED |
| Object |
Utrecht–Eindhoven railway corridor
The Utrecht–Eindhoven railway corridor is a major Dutch rail route linking the central city of Utrecht with the southern city of Eindhoven, serving as a key passenger and freight artery in the Netherlands.
|
E2139227
|
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: Utrecht–Eindhoven railway corridor | Statement: [North Brabant rail network, hasCorridor, Utrecht–Eindhoven railway corridor]
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: Utrecht–Eindhoven railway corridor Triple: [North Brabant rail network, hasCorridor, Utrecht–Eindhoven railway corridor]
Generated description
The Utrecht–Eindhoven railway corridor is a major Dutch rail route linking the central city of Utrecht with the southern city of Eindhoven, serving as a key passenger and freight artery in the Netherlands.
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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7915d005c8190b81056acf734fc67 |
completed | May 3, 2026, 6:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a382cae6b088190967b69e3299c4e67 |
completed | June 21, 2026, 6:25 p.m. |
| NEDg | Description generation | batch_6a382ebf5a448190932ddd9de2f11fdf |
completed | June 21, 2026, 6:34 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a382f19b6b88190826e0466924e770f |
completed | June 21, 2026, 6:36 p.m. |
Created at: May 3, 2026, 4:03 p.m.