Triple
T1400246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian National Railway |
E30762
|
entity |
| Predicate | privatizationDate |
P23781
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Canadian National Railway, privatizationDate, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privatizationDate Context triple: [Canadian National Railway, privatizationDate, 1995]
-
A.
privatizedOn
chosen
Indicates the date or point in time when an entity transitioned from public or state ownership/control to private ownership/control.
-
B.
nationalisationYear
Indicates the year in which an entity was taken into state ownership or control through nationalisation.
-
C.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
D.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
-
E.
acquisitionDate
Indicates the date on which one entity formally acquires or takes ownership of 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c39c4c148190997150996ca26a99 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.