Triple
T7134570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Trunk Pacific Railway |
E166272
|
entity |
| Predicate | nationalizationReason |
P75045
|
FINISHED |
| Object | insolvency |
—
|
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: insolvency | Statement: [Grand Trunk Pacific Railway, nationalizationReason, insolvency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalizationReason Context triple: [Grand Trunk Pacific Railway, nationalizationReason, insolvency]
-
A.
nationalised
Indicates that control or ownership of an entity has been transferred from private or non-state hands to the government or state.
-
B.
statusBeforeNationalization
Indicates the condition or classification an entity had prior to being nationalized.
-
C.
region after nationalisation
Indicates that a region is characterized or defined by its status or condition following a process of nationalisation.
-
D.
nationalisedOn
Indicates the date or point in time when an entity was taken into state ownership or control by a national government.
-
E.
typeOfNationalisation
Indicates the specific form or method by which an asset, industry, or entity is brought under national or state ownership or control.
- F. None of above. chosen
Provenance (4 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e68f15bc8190a4d82b8ee388f497 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:45 p.m.