Triple
T38687689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evander Holyfield vs. Bert Cooper |
E949163
|
entity |
| Predicate | holyfieldHometown |
P22139
|
FINISHED |
| Object | Atlanta, Georgia, United States |
—
|
NE NERFINISHED |
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: Atlanta, Georgia, United States | Statement: [Evander Holyfield vs. Bert Cooper, holyfieldHometown, Atlanta, Georgia, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holyfieldHometown Context triple: [Evander Holyfield vs. Bert Cooper, holyfieldHometown, Atlanta, Georgia, United States]
-
A.
hometownOfHonoree
Indicates that a specified place is the hometown (place of origin or long-term residence) of the honoree.
-
B.
hasHometownOf
chosen
Indicates that one entity has, as its hometown, the place represented by the other entity.
-
C.
hasBoyhoodHomeOf
Indicates that a particular place served as the home where a male person lived during his childhood.
-
D.
placeOfBirth
Indicates the location where a person or other entity was born.
-
E.
homeTownInSeries
Indicates that a character’s hometown is located within a particular fictional series or narrative universe.
- 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_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:33 p.m.