Triple
T26116407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etihad Guest Miles |
E658834
|
entity |
| Predicate | redeemedVia |
P12362
|
FINISHED |
| Object | Etihad mobile app |
—
|
NE NERFINISHED |
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: Etihad mobile app | Statement: [Etihad Guest Miles, redeemedVia, Etihad mobile app]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redeemedVia Context triple: [Etihad Guest Miles, redeemedVia, Etihad mobile app]
-
A.
redeemedBy
Indicates that something (such as a code, voucher, coupon, or offer) has been claimed, exchanged, or converted into its associated benefit or value by a particular entity.
-
B.
redeemedAs
Indicates that one entity is exchanged, converted, or claimed in return for another specified benefit, value, or status.
-
C.
redemptionType
chosen
Indicates the manner or method by which something (such as a benefit, reward, or obligation) can be redeemed or fulfilled.
-
D.
redemptionOptions
Indicates the ways or methods by which something (such as points, credits, or vouchers) can be redeemed or exchanged for value.
-
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_69f60ac86d908190bf582de7891fb4b3 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:05 p.m.