Triple

T6251610
Position Surface form Disambiguated ID Type / Status
Subject Appalachian dulcimer E140056 entity
Predicate hasHornbostelSachsNumber P69341 FINISHED
Object 314.122-5 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: 314.122-5 | Statement: [Appalachian dulcimer, hasHornbostelSachsNumber, 314.122-5]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHornbostelSachsNumber
Context triple: [Appalachian dulcimer, hasHornbostelSachsNumber, 314.122-5]
  • A. usesMusicalSystem
    Indicates that one entity employs or operates according to a particular musical system, framework, or set of musical rules.
  • B. hasSyllabary
    Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
  • C. hasOpusNumber
    Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
  • D. hasMusicalForm
    Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
  • E. hasLimitedConsonantInventory
    Indicates that a language possesses a relatively small set of distinct consonant sounds in its phonological system.
  • F. None of above. chosen

Provenance (4 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_69c008b4858c819095b0199114a9a87b completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0633fb2ac8190b71b8e35fa923300 completed March 22, 2026, 9:46 p.m.
PD Predicate disambiguation batch_69c056037bf88190a0a3fe7429345d0b completed March 22, 2026, 8:50 p.m.
PDg Predicate description generation batch_69c056df95ac8190bc5efe050d3af864 completed March 22, 2026, 8:53 p.m.
Created at: March 22, 2026, 4:24 p.m.