Triple
T35676680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oneworld partner airlines |
E1030878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airline partnership group |
C1909
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: airline partnership group Context triple: [oneworld partner airlines, instanceOf, airline partnership group]
-
A.
regional airline alliance
A regional airline alliance is a cooperative partnership among smaller, geographically focused airlines that coordinate schedules, share resources, and integrate services to expand network coverage and improve connectivity within a specific region.
-
B.
airline alliance partner flight
An airline alliance partner flight is a flight operated by one airline but marketed and sold under the flight number of another airline within the same alliance, allowing shared services, benefits, and coordinated schedules.
-
C.
airline association
An airline association is an organized group of airlines that collaborates to set industry standards, coordinate policies, and advocate for the collective interests of its member carriers.
-
D.
global airline alliance
chosen
A global airline alliance is a cooperative network of independent airlines that coordinate schedules, share services, and integrate frequent-flyer and marketing programs to offer passengers seamless international travel across their combined route systems.
-
E.
air cargo alliance
An air cargo alliance is a cooperative network of airlines and logistics partners that coordinate routes, capacity, and services to provide integrated, efficient global air freight transportation.
- F. None of above.
Provenance (1 batch)
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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.