Triple
T33842424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilma (clapsticks) |
E867390
|
entity |
| Predicate | HornbostelSachsClass |
P69341
|
FINISHED |
| Object | 111.11 |
—
|
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: 111.11 | Statement: [Bilma (clapsticks), HornbostelSachsClass, 111.11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HornbostelSachsClass Context triple: [Bilma (clapsticks), HornbostelSachsClass, 111.11]
-
A.
classifiedInHornbostelSachs
Indicates that something is assigned a category according to the Hornbostel-Sachs musical instrument classification system.
-
B.
hasHornbostelSachsNumber
chosen
Indicates that an entity (typically a musical instrument) is assigned a specific Hornbostel–Sachs classification number that encodes its type and method of sound production.
-
C.
hasHornbostelSachsDescription
Indicates that an entity is associated with a textual description of its classification according to the Hornbostel–Sachs musical instrument system.
-
D.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
-
E.
primaryInstrumentFamily
Indicates the main family or category of musical instruments with which an entity is primarily associated.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7005069dc8190a8473c015571a4a0 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.