Triple
T28249738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Air Lines loyalty program |
E712280
|
entity |
| Predicate | benefitIncludes |
P2188
|
FINISHED |
| Object | award travel |
—
|
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: award travel | Statement: [Delta Air Lines loyalty program, benefitIncludes, award travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitIncludes Context triple: [Delta Air Lines loyalty program, benefitIncludes, award travel]
-
A.
benefitsMayInclude
Indicates that one entity lists or specifies possible advantages, gains, or positive outcomes that another entity may receive.
-
B.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
C.
benefitCharacteristic
Indicates that one entity possesses a quality or feature that provides an advantage, usefulness, or positive effect to another entity.
-
D.
promotionIncludes
Indicates that a particular promotion encompasses, covers, or applies to a specified item, service, or condition.
-
E.
hasBenefit
chosen
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 11:03 p.m.