Triple
T22589512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Horizon |
E564902
|
entity |
| Predicate | cabinClassesOffered |
P127050
|
FINISHED |
| Object | First Class |
—
|
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: First Class | Statement: [Alaska Horizon, cabinClassesOffered, First Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cabinClassesOffered Context triple: [Alaska Horizon, cabinClassesOffered, First Class]
-
A.
cabinTypes
Indicates the types or categories of cabins associated with an entity, such as the different classes or configurations available.
-
B.
hasCabinClass
Indicates that an entity (such as a booking, ticket, or seat) is associated with a specific cabin class (e.g., economy, business, first).
-
C.
servesCabinClass
chosen
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).
-
D.
doesNotOfferCabinClass
Indicates that a service provider does not make a specific cabin class available for booking or use.
-
E.
hasCabins
Indicates that an entity possesses or includes one or more cabins as part of its structure or facilities.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615f63788190acf776b313f0794a |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:48 p.m.