Triple
T17334031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Traveller Plus |
E420888
|
entity |
| Predicate | positionInCabinHierarchy |
P5163
|
FINISHED |
| Object | between World Traveller and Club World |
—
|
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: between World Traveller and Club World | Statement: [World Traveller Plus, positionInCabinHierarchy, between World Traveller and Club World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCabinHierarchy Context triple: [World Traveller Plus, positionInCabinHierarchy, between World Traveller and Club World]
-
A.
seatInHierarchy
Indicates that one entity occupies a specific position or level within an ordered hierarchy relative to other entities.
-
B.
positionInHierarchy
chosen
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
-
C.
positionOnFlight
Indicates the specific seat or positional assignment that an entity has on a particular flight.
-
D.
positionInCascade
Indicates the specific step or level an element occupies within an ordered cascade or sequence of dependent stages.
-
E.
positionInSector
Indicates the specific location or placement of an entity within a defined sector or sub-area.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a106df48190a50f96febc13cde7 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.