Triple
T27513293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Airlines Mileage Plan |
E694476
|
entity |
| Predicate | allowsOneWayAwards |
P171426
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Alaska Airlines Mileage Plan, allowsOneWayAwards, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsOneWayAwards Context triple: [Alaska Airlines Mileage Plan, allowsOneWayAwards, true]
-
A.
mayBeAwardedWith
Indicates that an entity has the potential or eligibility to receive a particular award or distinction.
-
B.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
-
C.
canBeAwardedTo
Indicates that something is eligible to receive or be granted a particular award, honor, or recognition.
-
D.
hasOppositeAward
Indicates that one award is defined as the opposite or counterpart of another award.
-
E.
hasSeparateAwardFor
Indicates that there exists a distinct, dedicated award specifically recognizing the related entity, separate from other general or combined awards.
- F. None of above. chosen
Provenance (4 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 1:17 p.m.