Triple
T33929117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBF bantamweight title |
E869836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bantamweight boxing title |
C49137
|
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: bantamweight boxing title Context triple: [IBF bantamweight title, instanceOf, bantamweight boxing title]
-
A.
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).
-
B.
super bantamweight title
A super bantamweight title is a championship designation in professional boxing awarded to the top competitor in the weight class between bantamweight and featherweight, typically around 122 pounds (55.3 kg).
-
C.
lightweight boxing title
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.
-
D.
world bantamweight boxing champion
chosen
A world bantamweight boxing champion is a professional boxer who holds a recognized global title in the bantamweight weight class, typically around 118 pounds (53.5 kg), signifying they are the top competitor in that division.
-
E.
super middleweight boxing title
A super middleweight boxing title is a championship designation awarded to the top professional boxer competing in the super middleweight weight class, typically around 168 pounds (76.2 kg), by a recognized sanctioning body.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.