Triple
T803440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transavia France |
E17177
|
entity |
| Predicate | cabinClass |
P3037
|
FINISHED |
| Object | economy 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: economy class | Statement: [Transavia France, cabinClass, economy class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cabinClass Context triple: [Transavia France, cabinClass, economy class]
-
A.
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).
-
B.
cabinConfiguration
Indicates how the interior space of a vehicle, vessel, or aircraft is arranged and organized for occupants or cargo.
-
C.
hotelClass
Indicates the classification or rating level assigned to a hotel, such as its star category or quality tier.
-
D.
hasCabins
Indicates that an entity possesses or includes one or more cabins as part of its structure or facilities.
-
E.
seatCategory
Indicates the classification or type of a seat (e.g., by comfort level, price tier, or section) assigned to an entity.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.