Triple
T24766361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBF super bantamweight title |
E619592
|
entity |
| Predicate | measurementSystemForLimit |
P1872
|
FINISHED |
| Object | 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: pounds | Statement: [IBF super bantamweight title, measurementSystemForLimit, pounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: measurementSystemForLimit Context triple: [IBF super bantamweight title, measurementSystemForLimit, pounds]
-
A.
measurementSetting
Indicates the specific conditions, parameters, or configuration under which a measurement is taken or recorded.
-
B.
measureType
Indicates the specific kind or category of measurement that characterizes how a quantity or value is assessed.
-
C.
usesMeasurementSystem
chosen
Indicates that one entity adopts or applies a particular system of measurement defined by another entity.
-
D.
measuredAs
Indicates that one entity’s quantity, value, or property is expressed or recorded using another entity as its measurement or unit.
-
E.
typeOfMeasure
Indicates that one entity specifies the kind or category of measurement used to quantify or evaluate another entity.
- 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_69f410a6a5d08190b8f518b3cc13a2e7 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:28 a.m.