Triple
T8141893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Upgrade Certificates |
E190116
|
entity |
| Predicate | mayUpgradeTo |
P16805
|
FINISHED |
| Object | premium economy cabin |
—
|
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: premium economy cabin | Statement: [Global Upgrade Certificates, mayUpgradeTo, premium economy cabin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayUpgradeTo Context triple: [Global Upgrade Certificates, mayUpgradeTo, premium economy cabin]
-
A.
mayAdvanceTo
chosen
Indicates that one entity is permitted or eligible to progress, move, or be promoted to another specified state, level, or position.
-
B.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
C.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
D.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
E.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4442299881909db56f7475cbb99a |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:36 p.m.