Triple
T38687688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evander Holyfield vs. Bert Cooper |
E949163
|
entity |
| Predicate | cooperNickname |
P90791
|
FINISHED |
| Object | Smokin' |
—
|
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: Smokin' | Statement: [Evander Holyfield vs. Bert Cooper, cooperNickname, Smokin']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperNickname Context triple: [Evander Holyfield vs. Bert Cooper, cooperNickname, Smokin']
-
A.
MichaelCooperAllDefensiveTeam
Indicates that Michael Cooper was selected to an NBA All-Defensive Team in a given season.
-
B.
brotherNickname
Indicates that one person is known by a nickname specifically used by or associated with their brother.
-
C.
nicknameCoinedIn
Indicates that a particular nickname was first created, introduced, or came into use in a specified time or context.
-
D.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
E.
unofficialNickname
chosen
Indicates that one entity is informally or colloquially known by a non-official nickname represented by the other entity.
- 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.