Triple
T11842256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Heavyweight Champion |
E281681
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heavyweight boxing championship |
C10401
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: heavyweight boxing championship Context triple: [World Heavyweight Champion, instanceOf, heavyweight boxing championship]
-
A.
world heavyweight boxing champion
chosen
A world heavyweight boxing champion is the boxer recognized by a major sanctioning body as the top competitor in the heavyweight division, having won and defended the title in sanctioned championship bouts.
-
B.
heavyweight boxer
A heavyweight boxer is a professional fighter who competes in the highest weight division of boxing, relying on power, strength, and endurance to defeat opponents in sanctioned bouts.
-
C.
world welterweight boxing champion
A world welterweight boxing champion is the boxer who holds a recognized global title in the welterweight division, having won it by defeating the reigning champion or claiming a sanctioned vacant championship.
-
D.
world middleweight boxing champion
The world middleweight boxing champion is the boxer recognized as the top competitor globally in the middleweight division, having won and holding a major sanctioned world title at that weight class.
-
E.
world lightweight boxing champion
The world lightweight boxing champion is the boxer recognized as the top competitor globally in the lightweight division, having won and currently holding a major sanctioned world title at that weight class.
- F. None of above.
Provenance (1 batch)
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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.