Triple

T23946106
Position Surface form Disambiguated ID Type / Status
Subject Hornbostel–Sachs 314.122-4-6 E602917 entity
Predicate hasStructuralSubtype P154457 FINISHED
Object composite chordophone 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: composite chordophone | Statement: [Hornbostel–Sachs 314.122-4-6, hasStructuralSubtype, composite chordophone]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStructuralSubtype
Context triple: [Hornbostel–Sachs 314.122-4-6, hasStructuralSubtype, composite chordophone]
  • A. hasStructureType
    Indicates that an entity possesses or is classified by a specific structural type or configuration.
  • B. hasAncestralType
    Indicates that one type is derived from, or originates from, another more primitive or original type in an inheritance or lineage hierarchy.
  • C. hasSubproperty
    Indicates that one property is a more specific version of another property, inheriting its meaning and constraints.
  • D. hasMultipleSubclasses
    Indicates that a class or category is related to more than one distinct subclass within a hierarchy.
  • E. hasAbstractType
    Indicates that an entity is associated with or classified under a more general, conceptual type rather than a concrete or specific instance.
  • 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_69e2953e4924819093f1c24c03476b42 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d02dd0cc8190b32eb86bdfe0bf9a completed April 29, 2026, 9:32 a.m.
PD Predicate disambiguation batch_69f1615518088190a206f54e2fdb14a3 completed April 29, 2026, 1:39 a.m.
PDg Predicate description generation batch_69f16e348b548190b76e50f9b611f76d completed April 29, 2026, 2:34 a.m.
Created at: April 17, 2026, 9:13 p.m.