Triple
T14437217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elgin Fringe Festival |
E357995
|
entity |
| Predicate | usesTicketingModel |
P108991
|
FINISHED |
| Object | button-based 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: button-based admission | Statement: [Elgin Fringe Festival, usesTicketingModel, button-based admission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTicketingModel Context triple: [Elgin Fringe Festival, usesTicketingModel, button-based admission]
-
A.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
B.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
C.
hasTicketModel
chosen
Indicates that an entity is associated with or uses a particular ticket model or ticketing schema.
-
D.
hasTicketingAuthority
Indicates that an entity possesses the official power or permission to issue, manage, or control tickets for an event, service, or system.
-
E.
usesTicketValidatorType
Indicates that an entity employs or is associated with a specific type or category of ticket validation device or method.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914a45ec81909ab8ccf302047d7f |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.