Triple
T33320143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Global First |
E853113
|
entity |
| Predicate | cabinHierarchyPosition |
P93035
|
FINISHED |
| Object | above United BusinessFirst |
—
|
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 United BusinessFirst | Statement: [United Global First, cabinHierarchyPosition, above United BusinessFirst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cabinHierarchyPosition Context triple: [United Global First, cabinHierarchyPosition, above United BusinessFirst]
-
A.
cabinAbove
Indicates that one cabin is positioned vertically higher than another cabin.
-
B.
cabinLocation
Indicates the spatial or geographic location associated with a cabin.
-
C.
seatInHierarchy
Indicates that one entity occupies a specific position or level within an ordered hierarchy relative to other entities.
-
D.
cabinClassHierarchy
chosen
Indicates a hierarchical relationship between cabin classes, where one cabin class is ranked above or below another in terms of priority, service level, or status.
-
E.
cabinFloor
Indicates that one entity is the floor or floor level within a cabin associated with 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:33 a.m.