Triple
T26489257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBO lightweight title |
E664910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lightweight boxing world championship |
C31264
|
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: lightweight boxing world championship Context triple: [WBO lightweight title, instanceOf, lightweight boxing world championship]
-
A.
lightweight boxing title
chosen
A lightweight boxing title is a championship designation awarded to the top professional boxer competing within the lightweight weight class, typically around 135 pounds (61.2 kg), under a recognized sanctioning body.
-
B.
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.
-
C.
light welterweight boxing title
A light welterweight boxing title is a championship designation awarded to the top professional boxer competing in the light welterweight weight class, typically around 140 pounds (63.5 kg).
-
D.
light middleweight boxing title
A light middleweight boxing title is a championship designation awarded to the top professional boxer competing within the light middleweight weight class, typically around 154 pounds (69.9 kg), under a recognized sanctioning body.
-
E.
light heavyweight boxing championship
The light heavyweight boxing championship is a title contested between elite professional boxers within the light heavyweight weight limit, designating the top fighter in that division.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:32 a.m.