Triple
T35783937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAdvantage Platinum |
E1034512
|
entity |
| Predicate | tierPosition |
P37057
|
FINISHED |
| Object | mid-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: mid-tier | Statement: [AAdvantage Platinum, tierPosition, mid-tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierPosition Context triple: [AAdvantage Platinum, tierPosition, mid-tier]
-
A.
tierDeterminedBy
Indicates that the classification level or rank of one entity is decided or derived based on the properties, status, or outcome associated with another entity.
-
B.
rankTier
chosen
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
C.
tierConfiguration
Indicates how entities are organized or assigned into different levels or tiers according to a defined configuration or scheme.
-
D.
tierType
Indicates the classification level or rank assigned to an entity within a multi-level or hierarchical system.
-
E.
rankingPositions
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a227c0548190947c3a998e79f274 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.