Triple
T33787438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rikki Don't Lose That Number |
E865828
|
entity |
| Predicate | hasPercussionist |
P85583
|
FINISHED |
| Object | Victor Feldman |
—
|
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: Victor Feldman | Statement: [Rikki Don't Lose That Number, hasPercussionist, Victor Feldman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPercussionist Context triple: [Rikki Don't Lose That Number, hasPercussionist, Victor Feldman]
-
A.
hasDrummer
Indicates that one entity serves as the drummer for, or plays drums in, another entity such as a band or musical group.
-
B.
hasPowerfulPercussion
Indicates that an entity features or produces percussion that is notably strong, intense, or forceful in impact.
-
C.
hasRhythmSection
Indicates that an entity (such as a musical group or piece) includes or is associated with a rhythm section component.
-
D.
hasPianist
chosen
Indicates that an entity is associated with or features a pianist, typically specifying who performs the piano part in a work, event, or group.
-
E.
hasGuitarist
Indicates that an entity has, employs, or is associated with a guitarist as part of it.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 1, 2026, 1:45 a.m.