Triple
T5002268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mileage Plan |
E112400
|
entity |
| Predicate | earnPartnerType |
P15570
|
FINISHED |
| Object | Oneworld member airlines |
—
|
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: Oneworld member airlines | Statement: [Mileage Plan, earnPartnerType, Oneworld member airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnPartnerType Context triple: [Mileage Plan, earnPartnerType, Oneworld member airlines]
-
A.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
B.
hasPartnershipType
chosen
Indicates the specific kind or category of partnership relationship that exists between entities.
-
C.
employerType
Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
-
D.
businessPartner
Indicates a formal collaborative relationship between two entities that work together in a business context, typically sharing responsibilities, risks, or benefits.
-
E.
generalPartner
Indicates that one entity serves as a general partner of another entity within a partnership relationship.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.