Triple

T5002279
Position Surface form Disambiguated ID Type / Status
Subject Mileage Plan E112400 entity
Predicate redeemActivity P40855 FINISHED
Object award flights on Alaska Airlines 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 on Alaska Airlines | Statement: [Mileage Plan, redeemActivity, award flights on Alaska Airlines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: redeemActivity
Context triple: [Mileage Plan, redeemActivity, award flights on Alaska Airlines]
  • A. rewardRedemption chosen
    Indicates the act of exchanging accumulated rewards, points, or benefits for goods, services, or other forms of value.
  • B. 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.
  • 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. redeemabilityChangedTo
    Indicates that the redeemability status of something has been updated or changed to a new specified state.
  • E. rewardUse
    Indicates that one entity grants or provides a reward in response to the use or utilization 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_69bd4433d0b08190877e83959ef40d81 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7472a1dc8190942f568a81fdd961 completed March 20, 2026, 4:23 p.m.
PD Predicate disambiguation batch_69bd714aee2481908fb0dd5fa2daf3a1 completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:34 p.m.