Triple
T31096072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aqualandia water park |
E792529
|
entity |
| Predicate | hasTypeOfTicket |
P95742
|
FINISHED |
| Object | day 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: day ticket | Statement: [Aqualandia water park, hasTypeOfTicket, day ticket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfTicket Context triple: [Aqualandia water park, hasTypeOfTicket, day ticket]
-
A.
hasTicket
Indicates that an entity possesses or holds a ticket, typically granting access, entry, or a right to a service or event.
-
B.
hasTicketCategory
chosen
Indicates that an item, event, or access right is associated with a specific ticket category or type.
-
C.
hasTicketAccess
Indicates that an entity is permitted to view, use, or manage a particular ticket or set of tickets.
-
D.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
E.
hasTicketOption
Indicates that an entity offers or is associated with a particular ticket choice or type as an available option.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 29, 2026, 9:03 p.m.