Triple
T35985197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clash of Champions |
E1040689
|
entity |
| Predicate | hasRingAnnouncers |
P96644
|
FINISHED |
| Object | WWE ring announcers |
—
|
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 ring announcers | Statement: [Clash of Champions, hasRingAnnouncers, WWE ring announcers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRingAnnouncers Context triple: [Clash of Champions, hasRingAnnouncers, WWE ring announcers]
-
A.
hasRingAnnouncer
chosen
Indicates that an event, typically a combat or sports match, is associated with a specific ring announcer who introduces participants and makes formal announcements.
-
B.
hasAnnouncers
Indicates that one entity serves as the announcer or commentary provider for another entity, such as an event, program, or broadcast.
-
C.
hasRingConfiguration
Indicates that one entity possesses or exhibits a specific arrangement or pattern of rings in its structure or form.
-
D.
hasRing
Indicates that one entity possesses, wears, or is characterized by the presence of a ring.
-
E.
hasBells
Indicates that an entity possesses or is equipped with one or more bells.
- 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_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:07 p.m.