Triple
T14045318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Light, No Light |
E337940
|
entity |
| Predicate | usesPercussiveBeats |
P60129
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [No Light, No Light, usesPercussiveBeats, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPercussiveBeats Context triple: [No Light, No Light, usesPercussiveBeats, yes]
-
A.
percussion
Indicates that an entity produces sound by being struck, shaken, or otherwise hit, as in playing or functioning as a percussion instrument.
-
B.
percussionStyle
Indicates the specific manner or technique in which percussion is played or executed in a given context.
-
C.
hasDrumProgrammingBy
Indicates that the drum programming for a work (such as a song or track) is created or performed by a specified entity.
-
D.
usesMusicalElement
chosen
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
-
E.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de312df37081909f45ce3e219af5dc |
completed | April 14, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.