Triple
T6526115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hornbostel–Sachs 314.122-4-8 |
E151305
|
entity |
| Predicate | classifiesAs |
P24573
|
FINISHED |
| Object | 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: chordophone | Statement: [Hornbostel–Sachs 314.122-4-8, classifiesAs, chordophone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classifiesAs Context triple: [Hornbostel–Sachs 314.122-4-8, classifiesAs, chordophone]
-
A.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
B.
isClassifiedUnder
chosen
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
C.
classificationIncludes
Indicates that a broader classification category encompasses or contains a specified subclass, member, or element within its scope.
-
D.
usesClassificationCriteria
Indicates that one entity applies specific classification criteria to categorize, organize, or evaluate another entity.
-
E.
definesClassification
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ada77b448190b6e0e07494fb4dd3 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.