Triple
T9253913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Canada Express |
E222391
|
entity |
| Predicate | codeShare |
P6096
|
FINISHED |
| Object | uses Air Canada flight numbers |
—
|
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: uses Air Canada flight numbers | Statement: [Air Canada Express, codeShare, uses Air Canada flight numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeShare Context triple: [Air Canada Express, codeShare, uses Air Canada flight numbers]
-
A.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
B.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
-
C.
sharesCodebaseWith
Indicates that two software systems or components are built from, or depend on, substantially the same underlying source code.
-
D.
codeExample
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
-
E.
codeshareOperatesFor
chosen
Indicates that one airline operates a flight under a codeshare agreement on behalf of another airline, using the latter’s flight number or code.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b1f6bc81908115e22652d0c85e |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.