Triple
T28377193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomorrowland station |
E718783
|
entity |
| Predicate | hasTicketRequired |
P5937
|
FINISHED |
| Object | Disneyland park admission |
—
|
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: Disneyland park admission | Statement: [Tomorrowland station, hasTicketRequired, Disneyland park admission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketRequired Context triple: [Tomorrowland station, hasTicketRequired, Disneyland park admission]
-
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.
hasTicket
Indicates that an entity possesses or holds a ticket, typically granting access, entry, or a right to a service or event.
-
C.
hasTicketAccess
Indicates that an entity is permitted to view, use, or manage a particular ticket or set of tickets.
-
D.
hasTicketBarrier
Indicates that an access-controlled barrier or gate is present, typically requiring a valid ticket or pass to pass through.
-
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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 1:03 a.m.