Triple
T24345027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vueling |
E613615
|
entity |
| Predicate | loyaltyProgramLinkedTo |
P155797
|
FINISHED |
| Object | Avios |
—
|
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: Avios | Statement: [Vueling, loyaltyProgramLinkedTo, Avios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyProgramLinkedTo Context triple: [Vueling, loyaltyProgramLinkedTo, Avios]
-
A.
loyaltyProgramAccess
Indicates that an entity is granted rights or eligibility to participate in a specific loyalty or rewards program.
-
B.
associatedLoyaltyStatus
Indicates that there is a connection between an entity and a specific loyalty status within a loyalty or rewards program.
-
C.
hasLoyalties
Indicates that an entity feels allegiance or commitment toward one or more other entities or causes.
-
D.
loyaltyIntegration
Indicates the degree to which a loyalty or rewards program is connected, synchronized, or functionally embedded with another system, platform, or service.
-
E.
loyaltyProgramType
Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29328b0288190a580939e8863b0c2 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:58 a.m.