Triple
T31791599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ddr |
E811480
|
entity |
| Predicate | railwayLineContext |
P848
|
FINISHED |
| Object | railway lines serving Dordrecht railway station |
—
|
LITERAL 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: railway lines serving Dordrecht railway station | Statement: [Ddr, railwayLineContext, railway lines serving Dordrecht railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineContext Context triple: [Ddr, railwayLineContext, railway lines serving Dordrecht railway station]
-
A.
railwayLine
chosen
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
railwayLineLocation
Indicates that a railway line is located in, passes through, or is associated with a specific geographic area or place.
-
C.
railwayLineNow
Indicates that a previously existing railway line has been replaced, succeeded, or is currently represented by a new or different railway line.
-
D.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
E.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
- F. None of above.
Provenance (3 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 30, 2026, 11:39 p.m.