Triple
T19256332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian classical music |
E481523
|
entity |
| Predicate | hasTypicalDroneInstrument |
P24000
|
FINISHED |
| Object | tanpura |
—
|
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: tanpura | Statement: [Indian classical music, hasTypicalDroneInstrument, tanpura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalDroneInstrument Context triple: [Indian classical music, hasTypicalDroneInstrument, tanpura]
-
A.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
B.
includesInstruments
Indicates that one entity contains, involves, or makes use of one or more instruments as part of its composition or execution.
-
C.
hasMusicalInstrument
chosen
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
-
D.
hasInstrumentRole
Indicates that an entity participates in an action or process specifically in the capacity of an instrument or means by which that action is carried out.
-
E.
isNonVocalInstrumental
Indicates that an entity produces instrumental sound without involving vocalization.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb3572c08190a55f1c71cdb18b42 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.