Triple
T5192522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts Express ride |
E117189
|
entity |
| Predicate | ticketTypeRequired |
P46100
|
FINISHED |
| Object | multi-park ticket |
—
|
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: multi-park ticket | Statement: [Hogwarts Express ride, ticketTypeRequired, multi-park ticket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketTypeRequired Context triple: [Hogwarts Express ride, ticketTypeRequired, multi-park ticket]
-
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.
requiresParkTicket
chosen
Indicates that access to something is conditional on possessing a valid park ticket.
-
C.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
-
D.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
E.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79efd16c8190b0b16278a00baecd |
completed | March 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.