Triple
T38687677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evander Holyfield vs. Bert Cooper |
E949163
|
entity |
| Predicate | holyfieldKnockedDown |
P191531
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Evander Holyfield vs. Bert Cooper, holyfieldKnockedDown, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holyfieldKnockedDown Context triple: [Evander Holyfield vs. Bert Cooper, holyfieldKnockedDown, yes]
-
A.
roundOfKnockdown
Indicates the specific round in which a knockdown event occurs during a fight or match.
-
B.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
C.
tookHeavyDamageAt
Indicates that an entity experienced severe or substantial damage at a specific location or point in time.
-
D.
defendingChampionEliminatedIn
Indicates that the defending champion of a competition was eliminated in a specified round, stage, or edition of that competition.
-
E.
finalSmash
Indicates that one entity performs or activates a powerful, ultimate special attack or finishing move directed at another entity.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.