Triple
T33114035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somewhere Gone |
E847408
|
entity |
| Predicate | featuresVocalStyleOf |
P203326
|
FINISHED |
| Object | Exene Cervenka |
—
|
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: Exene Cervenka | Statement: [Somewhere Gone, featuresVocalStyleOf, Exene Cervenka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresVocalStyleOf Context triple: [Somewhere Gone, featuresVocalStyleOf, Exene Cervenka]
-
A.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
B.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice of another entity.
-
C.
featuresVocalHarmonyBy
Indicates that the subject work includes vocal harmony performances contributed by the specified artist or group.
-
D.
artisticVocalStyle
Indicates a relationship where an entity’s vocal performance is characterized by a particular artistic style or expressive manner of singing or speaking.
-
E.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
- F. None of above. chosen
Provenance (4 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a015ff02814819094806517fc4c69fa |
completed | May 11, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a0154ddd3c48190b85f9f48731cfd8f |
completed | May 11, 2026, 4:02 a.m. |
| PDg | Predicate description generation | batch_6a015fef7ae8819096c159ff0b259e1f |
completed | May 11, 2026, 4:49 a.m. |
Created at: May 1, 2026, 1:27 a.m.