Triple
T28077279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Hands |
E709577
|
entity |
| Predicate | hasChorusVocalLead |
P30369
|
FINISHED |
| Object | Roscoe Dash |
—
|
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: Roscoe Dash | Statement: [No Hands, hasChorusVocalLead, Roscoe Dash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChorusVocalLead Context triple: [No Hands, hasChorusVocalLead, Roscoe Dash]
-
A.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
B.
hasChorusIn
Indicates that a musical work includes a chorus section within the specified part or segment.
-
C.
hasChorusBy
chosen
Indicates that something (typically a musical work or song) includes a chorus section that is performed, written, or provided by a specified entity.
-
D.
containsChorusOf
Indicates that one entity (typically a musical work or section) includes within it a chorus performed by another entity (such as a group of singers or ensemble).
-
E.
hasChorusStyle
Indicates that an entity is associated with a particular style or manner in which a chorus is performed or structured.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 8:49 p.m.