Triple
T5824480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HawaiianMiles |
E129188
|
entity |
| Predicate | canRedeemFor |
P36375
|
FINISHED |
| Object | award flights |
—
|
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 flights | Statement: [HawaiianMiles, canRedeemFor, award flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRedeemFor Context triple: [HawaiianMiles, canRedeemFor, award flights]
-
A.
notRedeemableFor
Indicates that something cannot be exchanged, converted, or used to obtain another specified item, service, or benefit.
-
B.
allowsRedemptionFor
chosen
Indicates that one party grants another the right or ability to redeem something (such as a benefit, asset, or offer) under specified conditions.
-
C.
redeemableAt
Indicates that something (such as a voucher, coupon, or credit) can be exchanged for value or benefits at a specified place, platform, or entity.
-
D.
redeemableByAct
Indicates that something (such as a right, claim, or instrument) can be redeemed, exercised, or satisfied through a specific formal act or legal action.
-
E.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense of 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.