Triple
T31650360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Platinum |
E807711
|
entity |
| Predicate | statusComparison |
P131864
|
FINISHED |
| Object | higher than Platinum in ConnectMiles |
—
|
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: higher than Platinum in ConnectMiles | Statement: [Presidential Platinum, statusComparison, higher than Platinum in ConnectMiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusComparison Context triple: [Presidential Platinum, statusComparison, higher than Platinum in ConnectMiles]
-
A.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
B.
statusRelativeTo
chosen
Indicates the comparative state or condition of one entity in relation to another at a given point or over a period of time.
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 30, 2026, 10:53 p.m.