Triple
T30869928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EVAS Air |
E786307
|
entity |
| Predicate | operatedUnderRegionalBrand |
P68540
|
FINISHED |
| Object | Air Canada Express |
—
|
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: Air Canada Express | Statement: [EVAS Air, operatedUnderRegionalBrand, Air Canada Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUnderRegionalBrand Context triple: [EVAS Air, operatedUnderRegionalBrand, Air Canada Express]
-
A.
operatesBrandInRegion
Indicates that an entity manages or runs a specific brand within a particular geographic region.
-
B.
operatedByBrand
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
-
C.
operatesUnderFranchiseFrom
chosen
Indicates that one entity conducts its business or operations under the franchising rights, brand, and system granted by another entity.
-
D.
operatesUnderName
Indicates that an entity conducts its activities or business using a particular name, which may differ from its official or legal name.
-
E.
operatedChannelBrand
Indicates that a brand is responsible for operating or managing a particular channel.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: April 29, 2026, 8:47 p.m.