Triple
T21839513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lufthansa Regional |
E539215
|
entity |
| Predicate | bookingClassSystem |
P56945
|
FINISHED |
| Object | Lufthansa fare structure |
—
|
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: Lufthansa fare structure | Statement: [Lufthansa Regional, bookingClassSystem, Lufthansa fare structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingClassSystem Context triple: [Lufthansa Regional, bookingClassSystem, Lufthansa fare structure]
-
A.
ticketClassSystem
chosen
Indicates that an entity is classified within a particular ticketing or fare class system that defines categories or levels of tickets.
-
B.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
-
C.
bookingModel
Indicates a relationship where an entity uses or is associated with a specific model or schema that defines how bookings are structured, processed, or represented.
-
D.
bookingOption
Indicates a selectable arrangement or choice available for making a booking, such as a specific time, package, or set of conditions under which a reservation can be made.
-
E.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7aaa4f081909e869d2e81b07b91 |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.