Triple
T24766349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBF super bantamweight title |
E619592
|
entity |
| Predicate | sanctioningBodyAbbreviation |
P118927
|
FINISHED |
| Object | IBF |
—
|
NE NERFINISHED |
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: IBF | Statement: [IBF super bantamweight title, sanctioningBodyAbbreviation, IBF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctioningBodyAbbreviation Context triple: [IBF super bantamweight title, sanctioningBodyAbbreviation, IBF]
-
A.
abbreviationOfSanctioningBody
chosen
Indicates that one entity is the abbreviated or short-form name of another entity that serves as a sanctioning or governing body.
-
B.
laterSanctioningBody
Indicates that one entity serves as a subsequent or replacement sanctioning authority for another entity or event.
-
C.
fullSanctioningBodyName
Indicates that the object is the complete, official name of the organization that authoritatively sanctions or governs the subject.
-
D.
organizationTypeOfSanctioningBody
Indicates the type or category of organization that serves as the sanctioning body in a given context.
-
E.
sanctioningOrganization
Indicates the organization that formally imposes, authorizes, or enforces a sanction on another party.
- 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:28 a.m.