Triple
T4413069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Class cabins |
E94895
|
entity |
| Predicate | fareClass |
P9548
|
FINISHED |
| Object | higher than standard 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: higher than standard class | Statement: [Gold Class cabins, fareClass, higher than standard class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareClass Context triple: [Gold Class cabins, fareClass, higher than standard class]
-
A.
seatClass
Indicates the travel or seating category assigned to a passenger or seat (e.g., economy, business, first class).
-
B.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
-
C.
fareType
chosen
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
-
D.
fareProduct
Indicates a relationship where a specific fare or price offering is associated with a particular product or service option.
-
E.
fareTypes
Indicates the categories or kinds of fares (e.g., ticket or pricing options) that apply to a given travel or service offering.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e7b30c819082ee781dd202dcc4 |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.