Triple
T28684919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Way Down in the Hole |
E726104
|
entity |
| Predicate | hasKeyLyricMotive |
P85363
|
FINISHED |
| Object | keeping the devil way down in the hole |
—
|
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: keeping the devil way down in the hole | Statement: [Way Down in the Hole, hasKeyLyricMotive, keeping the devil way down in the hole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyLyricMotive Context triple: [Way Down in the Hole, hasKeyLyricMotive, keeping the devil way down in the hole]
-
A.
hasLyricPhrase
chosen
Indicates that one entity (typically a song or musical work) contains or is associated with a specific lyric phrase as part of its textual content.
-
B.
hasKeyLocationInLyrics
Indicates that a key or central location is mentioned or referenced within the lyrics.
-
C.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
D.
hasLyricCharacter
Indicates that a musical work or song includes a specific character or persona within its lyrics.
-
E.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 5:11 a.m.