Triple
T23715758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone |
E585996
|
entity |
| Predicate | hasCoLeadVocalsBy |
P25511
|
FINISHED |
| Object | Jerry Cantrell |
—
|
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: Jerry Cantrell | Statement: [Stone, hasCoLeadVocalsBy, Jerry Cantrell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoLeadVocalsBy Context triple: [Stone, hasCoLeadVocalsBy, Jerry Cantrell]
-
A.
coLeadVocalsBy
chosen
Indicates that the specified entity shares primary vocal duties on a performance or recording with one or more other lead vocalists.
-
B.
hasMaleLeadVocal
Indicates that the primary lead vocal in a performance, recording, or musical work is performed by a male singer.
-
C.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
-
D.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
E.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b77ab1bc8190be72606d363a07a0 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:54 p.m.