Triple
T32563133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier Miles |
E832280
|
entity |
| Predicate | hasStatusTiers |
P70212
|
FINISHED |
| Object | elite status levels |
—
|
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: elite status levels | Statement: [Frontier Miles, hasStatusTiers, elite status levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusTiers Context triple: [Frontier Miles, hasStatusTiers, elite status levels]
-
A.
hasProfessionalTiers
Indicates that an entity is organized into or associated with multiple levels or categories of professional status, service, or access.
-
B.
hasTierRestriction
Indicates that an entity is limited or governed by specific access or service tiers, restricting what applies at each tier.
-
C.
hasTierStructure
Indicates that something is organized into distinct hierarchical levels or layers within a structured system.
-
D.
hasProgramTier
Indicates that an entity is associated with a specific level or tier within a defined program or scheme.
-
E.
offersStatusLevels
chosen
Indicates that an entity provides or makes available different tiers or levels of status 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 1, 2026, 1:03 a.m.