Triple
T3300466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privilege Club |
E69317
|
entity |
| Predicate | earnMilesFrom |
P32734
|
FINISHED |
| Object | Qatar Airways flights |
—
|
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: Qatar Airways flights | Statement: [Privilege Club, earnMilesFrom, Qatar Airways flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnMilesFrom Context triple: [Privilege Club, earnMilesFrom, Qatar Airways flights]
-
A.
associatedWithFrequentFlyerProgram
Indicates that an entity has a connection or involvement with a frequent flyer program, such as membership, participation, or affiliation.
-
B.
mileageAccrual
chosen
Indicates the accumulation or earning of mileage (such as distance-based points or credits) as a result of certain actions or usage.
-
C.
loyaltyProgramEarnings
Indicates the amount or details of rewards or benefits a participant accrues within a loyalty or rewards program.
-
D.
airlinesUse
Indicates that certain airlines operate, employ, or make use of a specified resource, service, or system.
-
E.
fareAppliesTo
Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a66fcc819093931fe7a6507723 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.