Triple
T24765652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBC super bantamweight title |
E619574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | super bantamweight title |
C49136
|
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: super bantamweight title Context triple: [WBC super bantamweight title, instanceOf, super bantamweight title]
-
A.
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.
-
B.
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).
-
C.
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.
-
D.
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.
-
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. chosen
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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:28 a.m.