Triple
T21213630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LANPASS |
E522779
|
entity |
| Predicate | offersRedemptionOn |
P36375
|
FINISHED |
| Object | LAN Airlines 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: LAN Airlines flights | Statement: [LANPASS, offersRedemptionOn, LAN Airlines flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersRedemptionOn Context triple: [LANPASS, offersRedemptionOn, LAN Airlines flights]
-
A.
canBeRedeemedFor
Indicates that one item, asset, or benefit may be exchanged or converted to obtain another specified item, asset, or benefit.
-
B.
offersRewardFor
Indicates that one entity promises or provides a reward in exchange for another entity performing a specified action or achieving a particular outcome.
-
C.
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.
-
D.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
-
E.
rewardRedemption
Indicates the act of exchanging accumulated rewards, points, or benefits for goods, services, or other forms of value.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7347088488190aa764b3f4bbac44d |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:38 p.m.