Triple
T26116410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etihad Guest Miles |
E658834
|
entity |
| Predicate | supportsRedemptionType |
P12362
|
FINISHED |
| Object | one-way awards |
—
|
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: one-way awards | Statement: [Etihad Guest Miles, supportsRedemptionType, one-way awards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRedemptionType Context triple: [Etihad Guest Miles, supportsRedemptionType, one-way awards]
-
A.
allowsRedemptionFor
Indicates that one party grants another the right or ability to redeem something (such as a benefit, asset, or offer) under specified conditions.
-
B.
canBeRedeemedFor
Indicates that one item, asset, or benefit may be exchanged or converted to obtain another specified item, asset, or benefit.
-
C.
redemptionType
chosen
Indicates the manner or method by which something (such as a benefit, reward, or obligation) can be redeemed or fulfilled.
-
D.
notRedeemableFor
Indicates that something cannot be exchanged, converted, or used to obtain another specified item, service, or benefit.
-
E.
redemptionStatus
Indicates whether something that was previously issued, owed, or reserved has been claimed, fulfilled, or otherwise redeemed.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 26, 2026, 8:05 p.m.