Triple
T24765671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBC super bantamweight title |
E619574
|
entity |
| Predicate | weightClassCategory |
P105888
|
FINISHED |
| Object | lower weight class |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: lower weight class | Statement: [WBC super bantamweight title, weightClassCategory, lower weight class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightClassCategory Context triple: [WBC super bantamweight title, weightClassCategory, lower weight class]
-
A.
weightClass
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
B.
weightClassAlternativeName
Indicates that one weight class is referred to by an alternative name or label.
-
C.
weightClassBelow
chosen
Indicates that one entity belongs to a lower (lighter) weight class than another entity.
-
D.
intendedUserWeightClass
Indicates the weight category or range for which a user is specifically targeted or intended.
-
E.
launchWeightClass
Indicates the weight category or class into which a launch (typically of a vehicle, payload, or mission) is classified based on its mass.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:28 a.m.