Triple
T26529167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | saing waing ensemble |
E670771
|
entity |
| Predicate | hasCoreInstrumentType |
P186355
|
FINISHED |
| Object | tuned 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: tuned drums | Statement: [saing waing ensemble, hasCoreInstrumentType, tuned drums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreInstrumentType Context triple: [saing waing ensemble, hasCoreInstrumentType, tuned drums]
-
A.
hasInstrumentClass
Indicates that an action or process is carried out using an instrument that belongs to a specified class or category of instruments.
-
B.
hasInstrumentFamily
Indicates that an instrument is associated with a particular family or category of instruments (e.g., strings, brass, woodwinds).
-
C.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
D.
isInstrumentFor
Indicates that something is used as a tool or means to perform a particular action or achieve a specific outcome.
-
E.
belongsToInstrumentType
chosen
Indicates that something is classified under or associated with a particular type or category of 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 27, 2026, 1:34 a.m.