Triple
T23187422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hornbostel–Sachs |
E579628
|
entity |
| Predicate | classificationCodeFormat |
P508
|
FINISHED |
| Object | numeric |
—
|
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: numeric | Statement: [Hornbostel–Sachs, classificationCodeFormat, numeric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationCodeFormat Context triple: [Hornbostel–Sachs, classificationCodeFormat, numeric]
-
A.
labelCodeType
Indicates that one entity serves as the type or classification scheme for the labeling code applied to another entity.
-
B.
catalogCode
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
-
C.
numericCode
chosen
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
D.
segmentCode
Indicates a code that identifies or classifies a specific segment within a larger structure, sequence, or process.
-
E.
administrativeCodeSystem
Indicates that there is a system or scheme used to assign and manage administrative codes for organizing or identifying entities or records.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd4c6f481908b6138a44b98c8a7 |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.