Triple
T30238801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Cruz, Big Trees and Pacific Railway |
E768848
|
entity |
| Predicate | hasTicketingType |
P95742
|
FINISHED |
| Object | excursion tickets |
—
|
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: excursion tickets | Statement: [Santa Cruz, Big Trees and Pacific Railway, hasTicketingType, excursion tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketingType Context triple: [Santa Cruz, Big Trees and Pacific Railway, hasTicketingType, excursion tickets]
-
A.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
B.
hasTicketingStatus
Indicates the current ticketing state or condition associated with an entity, such as whether tickets are available, pending, confirmed, or canceled.
-
C.
hasTicketingAuthority
Indicates that an entity possesses the official power or permission to issue, manage, or control tickets for an event, service, or system.
-
D.
hasTicket
Indicates that an entity possesses or holds a ticket, typically granting access, entry, or a right to a service or event.
-
E.
hasTicketCategory
chosen
Indicates that an item, event, or access right is associated with a specific ticket category or type.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 29, 2026, 7:38 p.m.