Triple
T15508864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBO super bantamweight title |
E368652
|
entity |
| Predicate | weightRangeContext |
P26162
|
FINISHED |
| Object | between bantamweight and featherweight |
—
|
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: between bantamweight and featherweight | Statement: [WBO super bantamweight title, weightRangeContext, between bantamweight and featherweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightRangeContext Context triple: [WBO super bantamweight title, weightRangeContext, between bantamweight and featherweight]
-
A.
weightRangeDescription
chosen
Indicates the textual description that specifies the range within which an entity’s weight falls.
-
B.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
C.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
D.
rankRange
Indicates that an entity’s rank falls within a specified minimum and maximum range.
-
E.
weightSupport
Indicates that one entity bears or carries the physical weight of another, providing structural or mechanical support.
- 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_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. |
Created at: April 10, 2026, 3:55 a.m.