Triple
T28249675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SkyMiles Medallion tier |
E712278
|
entity |
| Predicate | benefitsIncreaseWith |
P111889
|
FINISHED |
| Object | higher Medallion tier level |
—
|
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: higher Medallion tier level | Statement: [SkyMiles Medallion tier, benefitsIncreaseWith, higher Medallion tier level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitsIncreaseWith Context triple: [SkyMiles Medallion tier, benefitsIncreaseWith, higher Medallion tier level]
-
A.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
B.
benefitsLevel
chosen
Indicates the degree or extent to which one entity gains advantages, support, or positive outcomes from another entity or action.
-
C.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
D.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
E.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 11:03 p.m.