Triple
T12314393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Park depot |
E293562
|
entity |
| Predicate | railwayDepotType |
P14646
|
FINISHED |
| Object | subsurface/Tube depot |
—
|
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: subsurface/Tube depot | Statement: [Queen's Park depot, railwayDepotType, subsurface/Tube depot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayDepotType Context triple: [Queen's Park depot, railwayDepotType, subsurface/Tube depot]
-
A.
depot
chosen
Indicates that an entity serves as a storage or distribution center location for another entity, such as goods, vehicles, or resources.
-
B.
railwayStationCategory
Indicates the classification or type category assigned to a railway station within a rail network or system.
-
C.
stationType
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
D.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
E.
hasRailYard
Indicates that one entity possesses, contains, or includes a rail yard as part of its facilities or infrastructure.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.