Triple
T37350363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IOC |
E927303
|
entity |
| Predicate | ownsRailway |
P96078
|
FINISHED |
| Object | Quebec North Shore and Labrador Railway |
—
|
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: Quebec North Shore and Labrador Railway | Statement: [IOC, ownsRailway, Quebec North Shore and Labrador Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownsRailway Context triple: [IOC, ownsRailway, Quebec North Shore and Labrador Railway]
-
A.
ownsRailwayLine
Indicates that one entity has legal ownership or control over a railway line used for train operations.
-
B.
railwayOwner
chosen
Indicates that one entity owns, controls, or holds proprietary rights over a railway or railway system used by another entity.
-
C.
hasPrivateRailway
Indicates that an entity owns or operates a railway line that is privately controlled rather than part of a public or national rail system.
-
D.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
E.
railwayCarriageOwner
Indicates that one entity is the owner or legal possessor of a particular railway carriage.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.