Triple
T25546527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Miles Platinum tier |
E640321
|
entity |
| Predicate | eliteLevelRank |
P37057
|
FINISHED |
| Object | top tier |
—
|
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: top tier | Statement: [Eastern Miles Platinum tier, eliteLevelRank, top tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliteLevelRank Context triple: [Eastern Miles Platinum tier, eliteLevelRank, top tier]
-
A.
eliteTierSystem
Indicates a relationship where entities are organized or classified into higher, privileged levels within a tiered ranking or status system.
-
B.
rankTier
chosen
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
C.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
D.
establishedRank
Indicates that a stable or officially recognized hierarchical position or level has been assigned to an entity relative to others.
-
E.
hasRankLevels
Indicates that an entity is associated with one or more hierarchical rank levels within a ranking or grading 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8992ce881909b95d520f580e231 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:34 p.m.