Triple
T23165851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamarudeen Usman |
E578708
|
entity |
| Predicate | titleReignType |
P151175
|
FINISHED |
| Object | dominant welterweight title reign |
—
|
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: dominant welterweight title reign | Statement: [Kamarudeen Usman, titleReignType, dominant welterweight title reign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleReignType Context triple: [Kamarudeen Usman, titleReignType, dominant welterweight title reign]
-
A.
titleReign
Indicates the period during which a particular title was officially held or exercised by an entity.
-
B.
titleReignCount
Indicates the number of times an entity has held or reigned with a particular title.
-
C.
typeOfMonarchyTitle
Indicates that a given title is a specific type or category of monarchy-related title (e.g., king, queen, emperor) within a monarchical system.
-
D.
reignTitleUsedTo
Indicates that a particular reign title was previously used to refer to or designate a given ruler, period, or authority.
-
E.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2bca4881909f6148d588948018 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:03 p.m.