Triple
T12531930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles+Bonus |
E299588
|
entity |
| Predicate | eliteTierQualificationMetric |
P12363
|
FINISHED |
| Object | tier miles |
—
|
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: tier miles | Statement: [Miles+Bonus, eliteTierQualificationMetric, tier miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteTierQualificationMetric Context triple: [Miles+Bonus, eliteTierQualificationMetric, tier miles]
-
A.
statusQualificationMetric
chosen
Indicates a metric that qualifies, evaluates, or characterizes the status or condition of something in a measurable way.
-
B.
eliteField
Indicates that the entity is associated with a highly selective or top-tier field, domain, or area of specialization.
-
C.
eliteStatusProgram
Indicates a relationship where an entity is enrolled in or associated with a special high-tier or privileged status program.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
qualificationFromTopDivision
Indicates that an entity has earned qualification originating from the highest (top) competitive division in a given hierarchy or system.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.