Triple
T31299088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sex Cymbal |
E798161
|
entity |
| Predicate | mainInstrumentEmphasis |
P17140
|
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: [Sex Cymbal, mainInstrumentEmphasis, drums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainInstrumentEmphasis Context triple: [Sex Cymbal, mainInstrumentEmphasis, drums]
-
A.
primaryInstrumentalFocus
chosen
Indicates that one entity serves as the main or most emphasized instrument or means by which another entity performs an action or achieves an effect.
-
B.
mainInstrumentFeatures
Indicates that the specified features characterize or describe the main instrument involved in an event or context.
-
C.
coreInstrument
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
-
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.
primaryInstrumentRole
Indicates that an entity serves as the main or leading instrument in a given role, context, or performance.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.