Triple
T28905889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byron Williams |
E733076
|
entity |
| Predicate | formerChampionOf |
P28766
|
FINISHED |
| Object | heavyweight boxing |
—
|
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: heavyweight boxing | Statement: [Byron Williams, formerChampionOf, heavyweight boxing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerChampionOf Context triple: [Byron Williams, formerChampionOf, heavyweight boxing]
-
A.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
-
B.
champion
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
C.
finalChampion
Indicates that an entity is the ultimate winner or last remaining champion in a competition or series of contests.
-
D.
notableFormerChampion
chosen
Indicates that an entity was once a champion of something and is recognized as particularly distinguished or prominent in that former champion role.
-
E.
championedBy
Indicates that an entity is actively supported, promoted, or advocated for by 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 28, 2026, 8:07 a.m.