Triple
T19528010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bielefeld viaduct |
E488581
|
entity |
| Predicate | railwayLineFunction |
P14634
|
FINISHED |
| Object | east–west freight traffic |
—
|
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: east–west freight traffic | Statement: [Bielefeld viaduct, railwayLineFunction, east–west freight traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineFunction Context triple: [Bielefeld viaduct, railwayLineFunction, east–west freight traffic]
-
A.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
railwayLineRole
chosen
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
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.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
E.
railwayLineSection
Indicates a specific segment or portion of a railway line that connects two points along the rail network.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363d43148190af25caaa57accf9b |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.