Triple
T6335221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Down in a Hole |
E142473
|
entity |
| Predicate | vocalHarmonyType |
P70922
|
FINISHED |
| Object | dual lead harmonies |
—
|
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: dual lead harmonies | Statement: [Down in a Hole, vocalHarmonyType, dual lead harmonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalHarmonyType Context triple: [Down in a Hole, vocalHarmonyType, dual lead harmonies]
-
A.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
B.
chorusType
Indicates the specific kind or category of chorus associated with an entity (e.g., type of vocal ensemble or choral grouping).
-
C.
vocalForces
Indicates a relationship where one entity uses vocal expression (such as speech, singing, or sound) to exert influence, pressure, or compulsion on another entity.
-
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.
melodyType
Indicates the specific kind or category of melody associated with or used by an entity.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654a88a881908d5cb2aa7f22c4c7 |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c064c080148190a7c3218867f1f572 |
completed | March 22, 2026, 9:53 p.m. |
Created at: March 22, 2026, 4:30 p.m.