Triple
T25025753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puntos Premier |
E626704
|
entity |
| Predicate | isRedeemableFor |
P110533
|
FINISHED |
| Object | experiences |
—
|
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: experiences | Statement: [Puntos Premier, isRedeemableFor, experiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRedeemableFor Context triple: [Puntos Premier, isRedeemableFor, experiences]
-
A.
canBeRedeemedFor
chosen
Indicates that one item, asset, or benefit may be exchanged or converted to obtain another specified item, asset, or benefit.
-
B.
notRedeemableFor
Indicates that something cannot be exchanged, converted, or used to obtain another specified item, service, or benefit.
-
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.
allowsRedemptionFor
Indicates that one party grants another the right or ability to redeem something (such as a benefit, asset, or offer) under specified conditions.
-
E.
isNonRedeemableByHolder
Indicates that the holder of an instrument, asset, or right is not permitted or able to redeem it for value, payment, or benefits.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:07 a.m.