Triple
T29463430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stop Trying to Be God |
E747306
|
entity |
| Predicate | harmonicaPerformer |
P140234
|
FINISHED |
| Object | Stevie Wonder |
—
|
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: Stevie Wonder | Statement: [Stop Trying to Be God, harmonicaPerformer, Stevie Wonder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harmonicaPerformer Context triple: [Stop Trying to Be God, harmonicaPerformer, Stevie Wonder]
-
A.
hornPlayer
Indicates that an entity plays, performs on, or is characterized as a player of a horn instrument in relation to another entity or context.
-
B.
associatedInstrumentalist
chosen
Indicates that an instrumentalist is connected to or involved with another entity, such as a work, performance, or recording, in a relevant musical role.
-
C.
bandLeader
Indicates that one entity serves as the leader or primary directing figure of a musical band that includes the other entity.
-
D.
chorusPerformer
Indicates that an entity performs as a member of the chorus in a musical or theatrical work.
-
E.
rhythmSectionPerformer
Indicates that a performer participates specifically as a member of the rhythm section within a musical ensemble.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66ba55eec8190ba43d3059b1ccaf6 |
completed | May 2, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:51 p.m.