Triple
T29997336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voice in the Night |
E762065
|
entity |
| Predicate | instrumentationOfBillyHiggins |
P12601
|
FINISHED |
| Object | drums |
—
|
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: drums | Statement: [Voice in the Night, instrumentationOfBillyHiggins, drums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentationOfBillyHiggins Context triple: [Voice in the Night, instrumentationOfBillyHiggins, drums]
-
A.
hasKeyInstrumentalist
Indicates that an entity (such as a musical work or performance) has a primary or featured instrumental performer associated with it.
-
B.
playedInstrument
chosen
Indicates that an entity performed or used a particular musical instrument.
-
C.
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.
-
D.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
-
E.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 6:40 p.m.