Triple
T30869927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EVAS Air |
E786307
|
entity |
| Predicate | operatedForMajorCarrier |
P35785
|
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: [EVAS Air, operatedForMajorCarrier, Air Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedForMajorCarrier Context triple: [EVAS Air, operatedForMajorCarrier, Air Canada]
-
A.
operatedForAirline
Indicates that an aircraft or flight was operated on behalf of, or under the branding of, a particular airline.
-
B.
airlineOperated
Indicates that a specific airline operates or runs a particular flight, route, or service.
-
C.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
D.
operatesFeederFlightsFor
Indicates that one airline or carrier runs connecting or short-haul feeder flights on behalf of, or in support of, another airline’s main services.
-
E.
operatesAsRegionalCarrierFor
chosen
Indicates that one transportation company functions as a regional carrier on behalf of another, typically providing local or feeder services under the larger company’s brand or network.
- 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_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: April 29, 2026, 8:47 p.m.