Triple
T38687678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evander Holyfield vs. Bert Cooper |
E949163
|
entity |
| Predicate | cooperKnockedDown |
P182909
|
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, cooperKnockedDown, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperKnockedDown Context triple: [Evander Holyfield vs. Bert Cooper, cooperKnockedDown, yes]
-
A.
wasStruckBy
chosen
Indicates that one entity received an impact or blow caused by another entity or force.
-
B.
fallsDownBefore
Indicates that one event or entity moves downward or collapses prior in time to another specified event or entity.
-
C.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
D.
fellWith
Indicates that one entity fell at the same time as, or in conjunction with, another entity.
-
E.
fallsOutWith
Indicates that one entity has a serious disagreement or conflict with another, resulting in the breakdown or loss of their previously friendly or cooperative relationship.
- 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.