Triple
T31333322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodstock |
E799092
|
entity |
| Predicate | ticketingOutcome |
P171252
|
FINISHED |
| Object | became a free concert due to crowd size |
—
|
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: became a free concert due to crowd size | Statement: [Woodstock, ticketingOutcome, became a free concert due to crowd size]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketingOutcome Context triple: [Woodstock, ticketingOutcome, became a free concert due to crowd size]
-
A.
ticketingContext
Indicates the situational or operational context in which a ticket (such as a support, event, or issue ticket) is created, managed, or applied.
-
B.
ticketingTreatment
Indicates how an entity is handled or processed within a ticketing or issue-tracking workflow.
-
C.
ticketingIssue
Indicates that there is a problem, error, or complication related to a ticketing process or ticket-based system.
-
D.
ticketingFor
Indicates that one entity is responsible for issuing, managing, or providing tickets for another entity, such as an event, service, or venue.
-
E.
ticketingPlan
Indicates the specific ticketing arrangement, policy, or scheme that governs how tickets are issued, priced, or managed for an event or service.
- F. None of above. chosen
Provenance (4 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f11ba548190b8ad25fafb07b62b |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69ea761848190acb31298e65b7892 |
completed | May 3, 2026, 1:02 a.m. |
Created at: April 29, 2026, 9:16 p.m.