Triple
T30869831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Regional Airlines |
E786305
|
entity |
| Predicate | operatedCodeShare |
P10967
|
FINISHED |
| Object | Air Canada |
—
|
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 | Statement: [Sky Regional Airlines, operatedCodeShare, Air Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedCodeShare Context triple: [Sky Regional Airlines, operatedCodeShare, Air Canada]
-
A.
airlineOperated
Indicates that a specific airline operates or runs a particular flight, route, or service.
-
B.
hasCodeShareOrInterline
chosen
Indicates that there exists a codeshare or interline agreement relationship between the referenced transportation services or carriers.
-
C.
operatingAirlineICAOCode
Indicates the ICAO airline designator code of the airline that is actually operating the flight or service.
-
D.
operatedForAirline
Indicates that an aircraft or flight was operated on behalf of, or under the branding of, a particular airline.
-
E.
operatingAirlineIATACode
Indicates the IATA airline code of the carrier that is actually operating the flight or air service.
- 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_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: April 29, 2026, 8:47 p.m.