Triple
T26111787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakeshore rail corridor |
E658716
|
entity |
| Predicate | ownedInSegmentsBy |
P90527
|
FINISHED |
| Object | Canadian Pacific Kansas City |
—
|
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: Canadian Pacific Kansas City | Statement: [Lakeshore rail corridor, ownedInSegmentsBy, Canadian Pacific Kansas City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedInSegmentsBy Context triple: [Lakeshore rail corridor, ownedInSegmentsBy, Canadian Pacific Kansas City]
-
A.
ownedInPartBy
Indicates that an entity holds a partial (non‑full) ownership stake in another entity.
-
B.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
-
C.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
-
D.
ownerOfRouteSegments
chosen
Indicates that an entity holds ownership or control over specific route segments within a network or pathway.
-
E.
ownershipRecordedBy
Indicates that the fact or status of ownership of an entity is documented or registered by a particular agent or system.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 8:02 p.m.