Triple
T21922977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEVEL |
E541365
|
entity |
| Predicate | loyaltyProgramAffiliation |
P37953
|
FINISHED |
| Object | IAG group frequent flyer ecosystem |
—
|
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: IAG group frequent flyer ecosystem | Statement: [LEVEL, loyaltyProgramAffiliation, IAG group frequent flyer ecosystem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyProgramAffiliation Context triple: [LEVEL, loyaltyProgramAffiliation, IAG group frequent flyer ecosystem]
-
A.
loyaltyProgramType
Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
-
B.
loyaltyProgramAccess
Indicates that an entity is granted rights or eligibility to participate in a specific loyalty or rewards program.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
hasLoyalties
Indicates that an entity feels allegiance or commitment toward one or more other entities or causes.
-
E.
loyaltyProgramName
chosen
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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233d096c8190af0d7cd21879c91b |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:45 p.m.