Triple
T7312660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean Air SKYPASS Million Miler |
E168131
|
entity |
| Predicate | statusLevelType |
P14125
|
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: [Korean Air SKYPASS Million Miler, statusLevelType, top-tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusLevelType Context triple: [Korean Air SKYPASS Million Miler, statusLevelType, top-tier]
-
A.
statusLevelAbove
Indicates that one entity’s status level is higher or more advanced than another entity’s status level.
-
B.
designationLevel
chosen
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
C.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
D.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
E.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ec02319c819096d25e3683943886 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.