Triple
T33677544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACA LifeMiles Diamond |
E862800
|
entity |
| Predicate | loyaltyProgramCurrency |
P107989
|
FINISHED |
| Object | LifeMiles |
—
|
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: LifeMiles | Statement: [TACA LifeMiles Diamond, loyaltyProgramCurrency, LifeMiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyProgramCurrency Context triple: [TACA LifeMiles Diamond, loyaltyProgramCurrency, LifeMiles]
-
A.
loyaltyCurrencyProgram
Indicates a relationship where an entity participates in or is associated with a loyalty or rewards currency program that tracks and grants benefits based on activity or purchases.
-
B.
loyaltyCurrencyUse
chosen
Indicates the use or redemption of loyalty program currency (such as points or miles) in a transaction or activity.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
loyaltyProgramType
Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
-
E.
loyaltyProgramName
Indicates that an entity is associated with or identified by the name of a specific loyalty or rewards program.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:43 a.m.