Triple
T34135893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | After the Storm |
E875564
|
entity |
| Predicate | containsSpokenOrAd-libVocalsBy |
P44280
|
FINISHED |
| Object | Bootsy Collins |
—
|
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: Bootsy Collins | Statement: [After the Storm, containsSpokenOrAd-libVocalsBy, Bootsy Collins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpokenOrAd-libVocalsBy Context triple: [After the Storm, containsSpokenOrAd-libVocalsBy, Bootsy Collins]
-
A.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
B.
isSpokenOrSung
Indicates that something (such as text, lyrics, or dialogue) is produced vocally, either by speaking or by singing.
-
C.
hasVocalPerformanceBy
chosen
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
D.
containsVocalSamplesFrom
Indicates that one audio work includes vocal samples that originate from another audio work.
-
E.
hasAdditionalVocalElements
Indicates that an entity includes extra vocal components or embellishments beyond its primary or standard vocal parts.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0059f4ffe481908dc500cee9051148 |
completed | May 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a00593a3c1881909b2ff1a29eb474b3 |
completed | May 10, 2026, 10:08 a.m. |
Created at: May 1, 2026, 1:53 a.m.