Triple
T9212267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardmore Station |
E221150
|
entity |
| Predicate | railCorridorType |
P86885
|
FINISHED |
| Object | busy passenger corridor |
—
|
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: busy passenger corridor | Statement: [Ardmore Station, railCorridorType, busy passenger corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railCorridorType Context triple: [Ardmore Station, railCorridorType, busy passenger corridor]
-
A.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
B.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
C.
partOfRailwayCorridor
Indicates that one entity is a segment, component, or area belonging to or contained within a specific railway corridor.
-
D.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
E.
hasRailwayInfrastructureType
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
- F. None of above. chosen
Provenance (4 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9b69838819088f33ca995fce222 |
completed | April 1, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc687067fc81909da2d78fda0cdcfb |
completed | April 1, 2026, 12:36 a.m. |
Created at: March 30, 2026, 7:27 p.m.