Triple
T20902203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Club Vistara |
E514699
|
entity |
| Predicate | pointsRedemptionType |
P110533
|
FINISHED |
| Object | flight tickets |
—
|
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: flight tickets | Statement: [Club Vistara, pointsRedemptionType, flight tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsRedemptionType Context triple: [Club Vistara, pointsRedemptionType, flight tickets]
-
A.
redemptionType
Indicates the manner or method by which something (such as a benefit, reward, or obligation) can be redeemed or fulfilled.
-
B.
rewardRedemption
Indicates the act of exchanging accumulated rewards, points, or benefits for goods, services, or other forms of value.
-
C.
canBeRedeemedFor
chosen
Indicates that one item, asset, or benefit may be exchanged or converted to obtain another specified item, asset, or benefit.
-
D.
redemptionOptions
Indicates the ways or methods by which something (such as points, credits, or vouchers) can be redeemed or exchanged for value.
-
E.
pointsEarnedFrom
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8fd7e4481909088b7f74ba24549 |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.