Triple
T38687691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evander Holyfield vs. Bert Cooper |
E949163
|
entity |
| Predicate | holyfieldNationality |
P104081
|
FINISHED |
| Object | American |
—
|
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: American | Statement: [Evander Holyfield vs. Bert Cooper, holyfieldNationality, American]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holyfieldNationality Context triple: [Evander Holyfield vs. Bert Cooper, holyfieldNationality, American]
-
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.
heroNationality
Indicates the country or national identity associated with a hero.
-
C.
opponentNationality
Indicates that the related entity is the country or nationality of the opponent in a competitive or adversarial context.
-
D.
championNationality
chosen
Indicates the country or nationality that a champion represents or is associated with.
-
E.
Sergio Pettis
Indicates a relationship or action involving the entity named "Sergio Pettis," such as participation, association, or attribution connected to him.
- 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_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:33 p.m.