Triple
T757633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montréal–Mirabel International Airport |
E15592
|
entity |
| Predicate | passengerServiceEnded |
P4906
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Montréal–Mirabel International Airport, passengerServiceEnded, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerServiceEnded Context triple: [Montréal–Mirabel International Airport, passengerServiceEnded, 2004]
-
A.
formerPassengerService
chosen
Indicates that an entity previously provided passenger transportation services but no longer does so.
-
B.
closedForPassengers
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
C.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
D.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
E.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66c2e108190a754c60d2eac6676 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.