Triple
T13056077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evil |
E327575
|
entity |
| Predicate | writerPerformerCombination |
P46708
|
FINISHED |
| Object | self-written and performed by Stevie Wonder |
—
|
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: self-written and performed by Stevie Wonder | Statement: [Evil, writerPerformerCombination, self-written and performed by Stevie Wonder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writerPerformerCombination Context triple: [Evil, writerPerformerCombination, self-written and performed by Stevie Wonder]
-
A.
writtenForPerformer
Indicates that a work was specifically composed or created to be performed by a particular performer or type of performer.
-
B.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
C.
writerOfMusicAndLyrics
chosen
Indicates that a person is the creator of both the musical composition and the song lyrics for a work.
-
D.
composedBy
Indicates that one entity is the creator or author of a musical or artistic work associated with another entity.
-
E.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:58 p.m.