Triple
T17334118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premium Voyageur |
E420889
|
entity |
| Predicate | fareIncludes |
P127047
|
FINISHED |
| Object | checked baggage allowance |
—
|
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: checked baggage allowance | Statement: [Premium Voyageur, fareIncludes, checked baggage allowance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareIncludes Context triple: [Premium Voyageur, fareIncludes, checked baggage allowance]
-
A.
cateringIncludes
Indicates that a catering service or arrangement encompasses or provides the specified item, service, or component as part of its offering.
-
B.
ticketIncludes
Indicates that a particular ticket grants access to, contains, or covers the specified item, service, or component.
-
C.
fiestaIncludes
Indicates that a particular fiesta or celebration event contains or features a specified element, such as an activity, performance, item, or participant.
-
D.
fareAppliesTo
Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
-
E.
diningPlanEligible
Indicates that an entity qualifies for or is allowed to participate in a specified dining plan.
- F. None of above. chosen
Provenance (4 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a106df48190a50f96febc13cde7 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.