Triple
T17454529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WZZ |
E424994
|
entity |
| Predicate | associatedAirlineAllianceStatus |
P25293
|
FINISHED |
| Object | non-alliance |
—
|
LITERAL FINISHED |
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: non-alliance | Statement: [WZZ, associatedAirlineAllianceStatus, non-alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirlineAllianceStatus Context triple: [WZZ, associatedAirlineAllianceStatus, non-alliance]
-
A.
airlineAllianceStatus
chosen
Indicates the formal alliance membership or partnership status that exists between an airline and an airline alliance.
-
B.
associatedAirlineType
Indicates a relationship where an airline is linked to a specific classification or type (e.g., carrier category or operational class).
-
C.
airlineAllianceMembership
Indicates that an airline is a member of a specific airline alliance.
-
D.
airlineAllianceRelationship
Indicates that two or more airlines are connected through a formal alliance or partnership arrangement.
-
E.
servesAirlineAllianceViaPrimaryCarrier
Indicates that a service or operation is provided under or on behalf of a specific airline alliance through the alliance’s designated primary carrier.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4514129f08190ae7581d2915a0373 |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.