Triple
T31145215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier CSeries test aircraft |
E793904
|
entity |
| Predicate | primaryTestBase |
P2909
|
FINISHED |
| Object | Montréal–Mirabel International Airport |
E15592
|
NE 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: Montréal–Mirabel International Airport | Statement: [Bombardier CSeries test aircraft, primaryTestBase, Montréal–Mirabel International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTestBase Context triple: [Bombardier CSeries test aircraft, primaryTestBase, Montréal–Mirabel International Airport]
-
A.
centralTest
Indicates that an entity serves as the primary or core test within a set of tests or an evaluation process.
-
B.
mainBase
chosen
Indicates that one entity serves as the primary or central base or headquarters for another entity.
-
C.
firstTest
Indicates that an entity is the initial or earliest test in a sequence or set of tests.
-
D.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
-
E.
establishedTest
Indicates that an entity has created, set up, or formally instituted a test or testing process.
- F. None of above.
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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b2d60ce788190998089f0a3211578 |
completed | June 11, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:06 p.m.