Triple
T33319863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Business |
E853108
|
entity |
| Predicate | cabinClassRelativeToPremiumEconomy |
P95734
|
FINISHED |
| Object | above Economy Plus |
—
|
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 Economy Plus | Statement: [United Business, cabinClassRelativeToPremiumEconomy, above Economy Plus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cabinClassRelativeToPremiumEconomy Context triple: [United Business, cabinClassRelativeToPremiumEconomy, above Economy Plus]
-
A.
cabinClassAbove
chosen
Indicates that one cabin class is ranked higher or more premium than another in a class hierarchy.
-
B.
cabinClassBelow
Indicates that one entity’s cabin class is ranked lower or less premium than another entity’s cabin class.
-
C.
comfortLevelRelativeToEconomy
Indicates the degree of comfort or quality relative to a standard economic or budget level.
-
D.
servesCabinClass
Indicates that a service provider (such as an airline or flight) offers or is available to a specified cabin class (e.g., economy, business, first).
-
E.
comfortLevelComparedToPremiumCabins
Indicates how the comfort level of something compares relative to that of premium cabins.
- 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_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:33 a.m.