Triple
T29997335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voice in the Night |
E762065
|
entity |
| Predicate | instrumentationOfDaveHolland |
P12601
|
FINISHED |
| Object | double bass |
—
|
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: double bass | Statement: [Voice in the Night, instrumentationOfDaveHolland, double bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentationOfDaveHolland Context triple: [Voice in the Night, instrumentationOfDaveHolland, double bass]
-
A.
instrumentsUsedBy
Indicates that a particular instrument, tool, or device is employed or utilized by a given entity to perform an action or achieve a result.
-
B.
coreInstrument
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
-
C.
playedInstrument
chosen
Indicates that an entity performed or used a particular musical instrument.
-
D.
instruments
Indicates that an agent uses a tool, device, or means to carry out an action or achieve an effect.
-
E.
designedInstrument
Indicates that an agent is responsible for creating or planning the design of a particular 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794c44c881908db0716b99c32481 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:40 p.m.