Triple
T3525017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Lottery |
E74516
|
entity |
| Predicate | ticketPurchaseRequirement |
P5937
|
FINISHED |
| Object | minimum age 18 |
—
|
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: minimum age 18 | Statement: [National Lottery, ticketPurchaseRequirement, minimum age 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketPurchaseRequirement Context triple: [National Lottery, ticketPurchaseRequirement, minimum age 18]
-
A.
hasTicketRequirement
chosen
Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
-
B.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
C.
requiresParkTicket
Indicates that access to something is conditional on possessing a valid park ticket.
-
D.
ticketPurchaseMethod
Indicates the method or channel through which a ticket was purchased (e.g., online, in person, via mobile app).
-
E.
theaterRequirement
Indicates that a certain condition, resource, or specification is required for a theater-related activity, production, or venue to be valid or properly supported.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc6a8d0c819094d38b9c47fb67b4 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.