Triple
T33796454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACA LifeMiles Elite |
E866086
|
entity |
| Predicate | hasTierType |
P69163
|
FINISHED |
| Object | high-tier status |
—
|
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: high-tier status | Statement: [TACA LifeMiles Elite, hasTierType, high-tier status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTierType Context triple: [TACA LifeMiles Elite, hasTierType, high-tier status]
-
A.
hasTierName
Indicates that an entity is associated with a specific tier by its name.
-
B.
hasTierStructure
Indicates that something is organized into distinct hierarchical levels or layers within a structured system.
-
C.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
-
D.
hasLevelType
chosen
Indicates that an entity is associated with a specific type or category of level (e.g., difficulty, hierarchy, or stage).
-
E.
hasTierRestriction
Indicates that an entity is limited or governed by specific access or service tiers, restricting what applies at each tier.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 1, 2026, 1:46 a.m.