Triple
T3300549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economy Class |
E69319
|
entity |
| Predicate | typicalBookingCode |
P42683
|
FINISHED |
| Object | Y |
—
|
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: Y | Statement: [Economy Class, typicalBookingCode, Y]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBookingCode Context triple: [Economy Class, typicalBookingCode, Y]
-
A.
bookingCodeType
Indicates the type or category of a booking code used to classify or identify a reservation.
-
B.
ticketingCode
chosen
Indicates the specific fare or booking code associated with a ticket that defines its pricing, rules, and conditions of use.
-
C.
airlineBookingChannel
Indicates the method or platform through which an airline reservation is made or managed between a customer and the airline.
-
D.
catalogCode
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
-
E.
typicalDestinationAirportIATA
Indicates the IATA airport code that is typically the destination in this kind of trip or route.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a66fcc819093931fe7a6507723 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.