Triple
T25305819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratford railway depot |
E634478
|
entity |
| Predicate | railwayDepotCode |
P18202
|
FINISHED |
| Object | SF |
—
|
NE NERFINISHED |
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: SF | Statement: [Stratford railway depot, railwayDepotCode, SF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayDepotCode Context triple: [Stratford railway depot, railwayDepotCode, SF]
-
A.
depot
Indicates that an entity serves as a storage or distribution center location for another entity, such as goods, vehicles, or resources.
-
B.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
-
C.
railroadCodeFor
chosen
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
D.
railwayDivisionHeadquartersOf
Indicates that one location serves as the administrative headquarters for a specified railway division.
-
E.
isRailwayStation
Indicates that the subject is a railway station, i.e., a facility where trains regularly stop to pick up or drop off passengers and/or freight.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4939a96e88190baf228db51101802 |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:25 p.m.