Triple
T25802896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vietnam Airlines Lotusmiles Titanium |
E649884
|
entity |
| Predicate | statusRank |
P152574
|
FINISHED |
| Object | below Vietnam Airlines Lotusmiles Platinum |
—
|
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: below Vietnam Airlines Lotusmiles Platinum | Statement: [Vietnam Airlines Lotusmiles Titanium, statusRank, below Vietnam Airlines Lotusmiles Platinum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusRank Context triple: [Vietnam Airlines Lotusmiles Titanium, statusRank, below Vietnam Airlines Lotusmiles Platinum]
-
A.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
-
B.
rankingStatus
Indicates the relative position or level an entity holds within an ordered ranking or hierarchy.
-
C.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
D.
rankIn
chosen
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
-
E.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 22, 2026, 6:42 a.m.