Triple
T1642978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyre Avenue Line |
E35514
|
entity |
| Predicate | openedAsRailway |
P16837
|
FINISHED |
| Object | 1912 |
—
|
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: 1912 | Statement: [Dyre Avenue Line, openedAsRailway, 1912]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsRailway Context triple: [Dyre Avenue Line, openedAsRailway, 1912]
-
A.
openedAsRailStop
Indicates that an entity began operation or was first established specifically as a railway stop.
-
B.
openedToRailTraffic
chosen
Indicates that a rail line, track, or related infrastructure has begun operating and is officially available for use by train traffic.
-
C.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
D.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
E.
formerRailwayLine
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.