Triple
T25166605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WCW World Television Championship |
E630196
|
entity |
| Predicate | bookingRole |
P157977
|
FINISHED |
| Object | workhorse title |
—
|
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: workhorse title | Statement: [WCW World Television Championship, bookingRole, workhorse title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingRole Context triple: [WCW World Television Championship, bookingRole, workhorse title]
-
A.
tourRole
Indicates the specific function, capacity, or responsibility an entity has within the context of a tour.
-
B.
audienceRole
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
C.
engagementRole
Indicates the specific function, capacity, or responsibility an entity assumes within a particular engagement or interaction.
-
D.
ticketDesignatorRole
Indicates the specific role or function associated with a ticket designator within a ticketing or fare context.
-
E.
roleInTheatreEcosystem
Indicates the specific function, responsibility, or position an entity holds within the interconnected system of theatre production, distribution, and audience engagement.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d42ec0081908231beebf495cf3e |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:17 p.m.