Triple
T10399903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Platinum |
E245117
|
entity |
| Predicate | statusLevelOrder |
P28991
|
FINISHED |
| Object | above Premier Gold |
—
|
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: above Premier Gold | Statement: [Premier Platinum, statusLevelOrder, above Premier Gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusLevelOrder Context triple: [Premier Platinum, statusLevelOrder, above Premier Gold]
-
A.
statusLevelAbove
chosen
Indicates that one entity’s status level is higher or more advanced than another entity’s status level.
-
B.
ordinationLevel
Indicates the hierarchical rank or degree of authority assigned to an entity within an ordered or structured system.
-
C.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
D.
statusUnderASC
Indicates that one entity has a particular accounting or reporting status as defined under ASC (Accounting Standards Codification) relative to another context or framework.
-
E.
offersStatusLevels
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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9d2e8488190b2bb8f8509903804 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:07 p.m.