Triple
T3127189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | See You in My Nightmares |
E65324
|
entity |
| Predicate | hasNotableVocalStyle |
P33230
|
FINISHED |
| Object | melodic rapping |
—
|
LITERAL FINISHED |
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: melodic rapping | Statement: [See You in My Nightmares, hasNotableVocalStyle, melodic rapping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVocalStyle Context triple: [See You in My Nightmares, hasNotableVocalStyle, melodic rapping]
-
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.
vocalPerformanceNotedFor
chosen
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
C.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
D.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
E.
hasSongStyle
Indicates that an entity possesses, is characterized by, or is associated with a particular style or genre of song.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada544cb648190b5ed430dbd561d52 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.