Triple
T19017210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort McMurray International Airport |
E465382
|
entity |
| Predicate | terminalOpened |
P80559
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Fort McMurray International Airport, terminalOpened, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalOpened Context triple: [Fort McMurray International Airport, terminalOpened, 2014]
-
A.
hasNewTerminalOpened
chosen
Indicates that a new terminal facility has begun operation or become available at a given location or entity.
-
B.
TerminalEUsedFor
Indicates that a terminal E is used for a particular purpose, function, or activity.
-
C.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
defaultTerminalEmulator
Indicates that one entity is configured or recognized as the standard or primary terminal emulator to be used by another entity 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6dc0f9081909cddc5186603e885 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.