Triple
T17645355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elst–Dordrecht railway |
E429341
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object | Elst |
—
|
NE NERFINISHED |
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: Elst | Statement: [Elst–Dordrecht railway, terminus, Elst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elst Context triple: [Elst–Dordrecht railway, terminus, Elst]
-
A.
Elst
Elst is a village in the Dutch municipality of Brakel, known as a small rural settlement in the province of Gelderland in the Netherlands.
-
B.
Elst
chosen
Elst is a town in the Netherlands that serves as a railway stop on the line between Arnhem and Nijmegen.
-
C.
Elstra
Elstra is a small town in the Bautzen district of the German federal state of Saxony.
-
D.
Elsterberg
Elsterberg is a small town in the Vogtland region of Saxony, Germany, known for its historic castle ruins and scenic location along the White Elster River.
-
E.
Elswit
Elswit is the surname of Robert Elswit, an acclaimed American cinematographer known for his work on films such as "There Will Be Blood."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e382ba88190af19d0e3b8c8cadd |
completed | April 19, 2026, 5:55 a.m. |
Created at: April 10, 2026, 6:04 a.m.