Triple
T31298990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sister Fate |
E798159
|
entity |
| Predicate | percussionistOnRecording |
P123791
|
FINISHED |
| Object | Sheila E. |
—
|
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: Sheila E. | Statement: [Sister Fate, percussionistOnRecording, Sheila E.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: percussionistOnRecording Context triple: [Sister Fate, percussionistOnRecording, Sheila E.]
-
A.
drummerOn
chosen
Indicates that one entity serves as the drummer or percussion performer for another entity, such as a band, ensemble, or musical project.
-
B.
rhythmSectionPerformer
Indicates that a performer participates specifically as a member of the rhythm section within a musical ensemble.
-
C.
percussionType
Indicates the specific kind or category of percussion instrument associated with an entity.
-
D.
percussion
Indicates that an entity produces sound by being struck, shaken, or otherwise hit, as in playing or functioning as a percussion instrument.
-
E.
usesDrums
Indicates that an entity employs drums as instruments or tools in performing an action or carrying out an activity.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.