Triple
T17110767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Majestic (1890) |
E415217
|
entity |
| Predicate | passengerClass |
P3037
|
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: [SS Majestic (1890), passengerClass, first class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerClass Context triple: [SS Majestic (1890), passengerClass, first class]
-
A.
seatClass
Indicates the travel or seating category assigned to a passenger or seat (e.g., economy, business, first class).
-
B.
airlineClass
Indicates the specific travel class or service level assigned to a passenger or ticket on an airline flight.
-
C.
aircraftSeatingCategory
Indicates the classification of an aircraft’s seating arrangement or capacity type associated with an entity.
-
D.
cabinClassAbove
Indicates that one cabin class is ranked higher or more premium than another in a class hierarchy.
-
E.
hasCabinClass
chosen
Indicates that an entity (such as a booking, ticket, or seat) is associated with a specific cabin class (e.g., economy, business, first).
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2a7f2c81908eb19594b6accab7 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.