Triple
T17381908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Club miles |
E422588
|
entity |
| Predicate | loyaltyProgramTierDependent |
P127274
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Flying Club miles, loyaltyProgramTierDependent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyProgramTierDependent Context triple: [Flying Club miles, loyaltyProgramTierDependent, yes]
-
A.
loyaltyProgramTierOf
Indicates the specific loyalty or rewards program tier that an entity (such as a customer or account) belongs to.
-
B.
loyaltyProgramAccess
Indicates that an entity is granted rights or eligibility to participate in a specific loyalty or rewards program.
-
C.
loyaltyProgramType
Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
-
D.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
-
E.
loyaltyDimension
Indicates the degree or aspect of loyalty characterizing the relationship between entities.
- F. None of above. chosen
Provenance (4 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a86d8cc81909281b22f5da87d70 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.