Triple
T12558168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergey Kovalev |
E295271
|
entity |
| Predicate | isMultipleTimeChampionIn |
P99897
|
FINISHED |
| Object | light heavyweight division |
—
|
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: light heavyweight division | Statement: [Sergey Kovalev, isMultipleTimeChampionIn, light heavyweight division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultipleTimeChampionIn Context triple: [Sergey Kovalev, isMultipleTimeChampionIn, light heavyweight division]
-
A.
hasWonMultipleChampionships
chosen
Indicates that the subject has secured championship titles on more than one separate occasion.
-
B.
firstTimeChampion
Indicates that an entity has won a championship title for the first time in its history.
-
C.
championRegularSeasonWins
Indicates that an entity is the champion based on having the highest number of regular season wins.
-
D.
hasChampionships
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
E.
hasDoublesChampionEachYear
Indicates that for each year in consideration, there exists at least one recognized doubles champion associated with that year.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:48 p.m.