Triple
T30869820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Regional Airlines |
E786305
|
entity |
| Predicate | operatedUnderBrandFrom |
P32898
|
FINISHED |
| Object | Air Canada Express, 2011 |
—
|
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, 2011 | Statement: [Sky Regional Airlines, operatedUnderBrandFrom, Air Canada Express, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUnderBrandFrom Context triple: [Sky Regional Airlines, operatedUnderBrandFrom, Air Canada Express, 2011]
-
A.
operatedByBrand
chosen
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
-
B.
laterBrandOf
Indicates that one brand is a subsequent or successor brand to another, coming into use at a later time.
-
C.
nowUnderBrand
Indicates that an entity is currently operating, marketed, or managed under a specified brand.
-
D.
operatedChannelBrand
Indicates that a brand is responsible for operating or managing a particular channel.
-
E.
usedBrandOf
Indicates that one entity made use of or operated an item, product, or service associated with a particular brand.
- 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_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: April 29, 2026, 8:47 p.m.