Triple
T12306111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBC lightweight title |
E293356
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | world boxing championship title |
C11240
|
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: world boxing championship title Context triple: [WBC lightweight title, instanceOf, world boxing championship title]
-
A.
world heavyweight boxing champion
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.
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.
-
C.
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.
-
D.
world lightweight boxing champion
chosen
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.
-
E.
world featherweight boxing champion
The world featherweight boxing champion is the boxer recognized as the top competitor globally in the featherweight division, having won and holding an officially 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.