Triple
T15508847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBO super bantamweight title |
E368652
|
entity |
| Predicate | divisionUpperLimit |
P118928
|
FINISHED |
| Object | 122 pounds |
—
|
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: 122 pounds | Statement: [WBO super bantamweight title, divisionUpperLimit, 122 pounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionUpperLimit Context triple: [WBO super bantamweight title, divisionUpperLimit, 122 pounds]
-
A.
divisionAbove
Indicates that one entity is positioned in a higher or superior division, tier, or level relative to another entity.
-
B.
divisionSize
Indicates the size or magnitude of a division or subdivided part in relation to a whole.
-
C.
parallelDivision
Indicates that one entity is divided or partitioned in a way that runs parallel to the division or partitioning of another entity.
-
D.
topDivisionAbove
Indicates that one division or tier is hierarchically higher or superior to another within an organizational or structural ranking.
-
E.
divisionContext
Indicates the situational or conceptual setting in which a division operation or separation between entities takes place.
- F. None of above. chosen
Provenance (4 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03fd008708190a3657863eb9ac626 |
completed | April 16, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:55 a.m.