Triple
T26582144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Air |
E667105
|
entity |
| Predicate | allianceOrMerger |
P600
|
FINISHED |
| Object | Canadian North |
—
|
NE NERFINISHED |
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: Canadian North | Statement: [First Air, allianceOrMerger, Canadian North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceOrMerger Context triple: [First Air, allianceOrMerger, Canadian North]
-
A.
allianceAfterAbsorption
Indicates that an alliance relationship is formed between entities after one has absorbed or taken over the other.
-
B.
alliance
chosen
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
C.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
D.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
E.
foundedByMergerOf
Indicates that an entity was created through the merger or combination of two or more predecessor entities.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:03 a.m.