Triple
T35177253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port McNicoll |
E1015740
|
entity |
| Predicate | railYardPresence |
P18851
|
FINISHED |
| Object | historic CPR rail yard |
—
|
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: historic CPR rail yard | Statement: [Port McNicoll, railYardPresence, historic CPR rail yard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railYardPresence Context triple: [Port McNicoll, railYardPresence, historic CPR rail yard]
-
A.
hasRailYard
chosen
Indicates that one entity possesses, contains, or includes a rail yard as part of its facilities or infrastructure.
-
B.
railPosition
Indicates the relative location or alignment of something with respect to a rail or set of rails.
-
C.
railStatus
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
-
D.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
E.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d7802b08190bec1695d4bb2d158 |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.