Triple
T17454573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WIZZ Discount Club |
E424995
|
entity |
| Predicate | appliesToFareType |
P8859
|
FINISHED |
| Object | WIZZ Discount Club fares |
—
|
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: WIZZ Discount Club fares | Statement: [WIZZ Discount Club, appliesToFareType, WIZZ Discount Club fares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToFareType Context triple: [WIZZ Discount Club, appliesToFareType, WIZZ Discount Club fares]
-
A.
fareAppliesTo
Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
-
B.
appliesToTransportMode
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular mode of transport.
-
C.
partOfFareStructure
Indicates that one element is included as a component within a larger fare structure or pricing scheme.
-
D.
fareType
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
-
E.
fareTypes
chosen
Indicates the categories or kinds of fares (e.g., ticket or pricing options) that apply to a given travel or service offering.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4514129f08190ae7581d2915a0373 |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.