Triple
T33319799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlusPoints upgrade currency |
E853106
|
entity |
| Predicate | revenueTicketRequired |
P73217
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [PlusPoints upgrade currency, revenueTicketRequired, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revenueTicketRequired Context triple: [PlusPoints upgrade currency, revenueTicketRequired, true]
-
A.
hasTicketRequirement
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
B.
isFreeStandingTicketRequired
Indicates whether a separate, stand-alone ticket is required for the related item or service.
-
C.
ticketSupplementRequired
chosen
Indicates that an additional ticket or fare supplement is required beyond the standard ticket for a given journey or service.
-
D.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
E.
requiresParkTicket
Indicates that access to something is conditional on possessing a valid park ticket.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.