Triple
T35722979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UP Comedy Club |
E1032529
|
entity |
| Predicate | hasBoxOfficeModel |
P195982
|
FINISHED |
| Object | advance ticket sales |
—
|
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: advance ticket sales | Statement: [UP Comedy Club, hasBoxOfficeModel, advance ticket sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoxOfficeModel Context triple: [UP Comedy Club, hasBoxOfficeModel, advance ticket sales]
-
A.
hasBoxOfficeType
Indicates the classification of a work’s box office performance or revenue category (e.g., type or scale of its box office results).
-
B.
hasBoxOffice
Indicates that an entity (typically a film or performance) has a specific box office revenue amount or record associated with it.
-
C.
boxOfficeStatus
Indicates the commercial performance or financial success status of a film or media release at the box office.
-
D.
boxOfficeReportingUnit
Indicates the unit or scale (e.g., currency, region, or measurement basis) in which box office revenue figures are reported.
-
E.
hasBoxOfficePhone
Indicates that an entity has a phone number specifically designated for its box office.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
| PDg | Predicate description generation | batch_69fdfbae00e481908a2e4558b9dee07e |
completed | May 8, 2026, 3:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.