Triple
T23716132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | So Far Under |
E586008
|
entity |
| Predicate | isRiffDriven |
P153678
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [So Far Under, isRiffDriven, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRiffDriven Context triple: [So Far Under, isRiffDriven, true]
-
A.
hasRiffs
Indicates that one entity features or contains musical riffs associated with another entity.
-
B.
hasRiffType
Indicates that one entity is characterized by, or associated with, a specific type or category of riff.
-
C.
isPianoDriven
Indicates that something is primarily led, dominated, or characterized by the piano in its musical arrangement or performance.
-
D.
isGuitarDriven
Indicates that something (such as a song, piece of music, or performance) is primarily led, dominated, or characterized by the sound and role of the guitar.
-
E.
hasMainRiff
Indicates that one musical piece, section, or track features another musical phrase or pattern as its primary recurring riff.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b77ab1bc8190be72606d363a07a0 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 6:54 p.m.