Triple
T17454555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WIZZ Discount Club |
E424995
|
entity |
| Predicate | membershipFeeType |
P37869
|
FINISHED |
| Object | annual fee |
—
|
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: annual fee | Statement: [WIZZ Discount Club, membershipFeeType, annual fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipFeeType Context triple: [WIZZ Discount Club, membershipFeeType, annual fee]
-
A.
clubMembershipType
Indicates the specific category or level of membership that an entity holds within a club.
-
B.
membershipCost
Indicates the monetary amount required to obtain or maintain membership in something.
-
C.
feeType
chosen
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
D.
membershipStructure
Indicates the organizational or hierarchical arrangement that defines how members are grouped, related, and governed within a collective or system.
-
E.
chargesMembershipFee
Indicates that an entity requires another entity to pay a membership fee in order to access its services, benefits, or participation.
- 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.