Triple
T25996975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kell Brook |
E646510
|
entity |
| Predicate | movedUpInWeightToFight |
P157294
|
FINISHED |
| Object | Gennady Golovkin |
—
|
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: Gennady Golovkin | Statement: [Kell Brook, movedUpInWeightToFight, Gennady Golovkin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedUpInWeightToFight Context triple: [Kell Brook, movedUpInWeightToFight, Gennady Golovkin]
-
A.
movedUpInWeightTo
chosen
Indicates that an entity has transitioned to compete or operate in a higher weight category than before.
-
B.
successorInUFCPromotion
Indicates that one entity directly follows another as the next promotion event or stage within the UFC organization.
-
C.
weightDivisionAbove
Indicates that one entity competes in or belongs to a higher weight division or class than another entity.
-
D.
hasFoughtInPromotion
Indicates that an entity (such as a fighter) has participated in at least one fight under a specific promotion or fighting organization.
-
E.
promotedToTopFlight
Indicates that an entity (such as a team or competitor) has been elevated from a lower division or level to the highest tier of competition.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6056f481c81909fd23b04483b76a0 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:58 a.m.