Triple
T15340711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ring super bantamweight title |
E366785
|
entity |
| Predicate | hasWeightRangeUpperBound |
P26160
|
FINISHED |
| Object | 122 lb |
—
|
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 lb | Statement: [The Ring super bantamweight title, hasWeightRangeUpperBound, 122 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeightRangeUpperBound Context triple: [The Ring super bantamweight title, hasWeightRangeUpperBound, 122 lb]
-
A.
hasMinimumWeight
Indicates that an entity’s weight meets or exceeds a specified minimum threshold.
-
B.
weightLimitInPounds
chosen
Indicates the maximum allowable weight for something, expressed in pounds.
-
C.
weightLimitInKilograms
Indicates the maximum allowable weight for something, expressed in kilograms.
-
D.
weightSupport
Indicates that one entity bears or carries the physical weight of another, providing structural or mechanical support.
-
E.
weightRangeDescription
Indicates the textual description that specifies the range within which an entity’s weight falls.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e12eb7c8190944a260aa1aa9156 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.