Triple
T38687679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evander Holyfield vs. Bert Cooper |
E949163
|
entity |
| Predicate | holyfieldKnockdownRound |
P101809
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Evander Holyfield vs. Bert Cooper, holyfieldKnockdownRound, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holyfieldKnockdownRound Context triple: [Evander Holyfield vs. Bert Cooper, holyfieldKnockdownRound, 3]
-
A.
holyfieldKnockedDown
Indicates that Holyfield caused another participant to be knocked down, typically by delivering a blow that sent them to the canvas in a fight.
-
B.
roundOfKnockdown
chosen
Indicates the specific round in which a knockdown event occurs during a fight or match.
-
C.
numberOfKnockouts
Indicates the total count of times an entity has defeated opponents by knockout.
-
D.
roundOfChampionship
Indicates the specific stage or round within a championship competition in which an event, match, or result takes place.
-
E.
numberOfKnockdowns
Indicates the count of times an entity has been knocked down during a specified event or interaction.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:33 p.m.