Triple
T24204755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Booker T |
E600074
|
entity |
| Predicate | workedAsCommentatorFor |
P13626
|
FINISHED |
| Object | WWE SmackDown |
—
|
NE NERFINISHED |
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: WWE SmackDown | Statement: [Booker T, workedAsCommentatorFor, WWE SmackDown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedAsCommentatorFor Context triple: [Booker T, workedAsCommentatorFor, WWE SmackDown]
-
A.
coCommentatorWith
Indicates that two individuals serve together as commentators on the same event, program, or broadcast.
-
B.
commentatorCountry
Indicates the country with which a commentator is associated, such as their nationality or the nation they represent.
-
C.
commentator
chosen
Indicates that an entity provides spoken or written real-time explanation, analysis, or opinion about an event, action, or content involving another entity.
-
D.
usesCommentaryTeamsOf
Indicates that one entity employs or relies on the commentary teams associated with another entity for coverage or presentation.
-
E.
sportCommentated
Indicates that one entity provides live or recorded commentary on a sporting event involving another entity.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca52cb881908c99913ea93bc88e |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.