Triple
T35985198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clash of Champions |
E1040689
|
entity |
| Predicate | hasCommentaryTeam |
P111241
|
FINISHED |
| Object | WWE commentary team |
—
|
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: WWE commentary team | Statement: [Clash of Champions, hasCommentaryTeam, WWE commentary team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommentaryTeam Context triple: [Clash of Champions, hasCommentaryTeam, WWE commentary team]
-
A.
usesCommentaryTeamsOf
Indicates that one entity employs or relies on the commentary teams associated with another entity for coverage or presentation.
-
B.
includesCommentaryTeam
chosen
Indicates that an entity has, as part of its composition or assignment, a specific commentary team associated with it.
-
C.
hasCommentaryIn
Indicates that an entity is discussed, analyzed, or annotated within a specific commentary work or source.
-
D.
hasCommentaryOn
Indicates that one entity provides commentary, explanation, or evaluative remarks about another entity.
-
E.
hasCommentaryForm
Indicates that one entity exists in, or is associated with, a commentary version or format of 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.