Triple
T17651857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnipeg James Armstrong Richardson International Airport |
E429509
|
entity |
| Predicate | newTerminalOpened |
P80559
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Winnipeg James Armstrong Richardson International Airport, newTerminalOpened, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newTerminalOpened Context triple: [Winnipeg James Armstrong Richardson International Airport, newTerminalOpened, 2011]
-
A.
hasNewTerminalOpened
chosen
Indicates that a new terminal facility has begun operation or become available at a given location or entity.
-
B.
newPassengerTerminalOpened
Indicates that a new passenger terminal has begun operations and is now open for use.
-
C.
openedAsTerminus
Indicates that a transportation line or route was initially opened with this location serving as its end-point terminus.
-
D.
usedTerminal
Indicates that an entity made use of or interacted with a particular terminal or endpoint device.
-
E.
closedAsTerminal
Indicates that a process, case, or interaction has been concluded in a final, non-reopenable (terminal) state.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3e0ae481908382570f802d8144 |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:05 a.m.