Triple
T37493328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 417a |
E931756
|
entity |
| Predicate | hasCatalogueNumberType |
P195085
|
FINISHED |
| Object | Köchel catalogue number |
—
|
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: Köchel catalogue number | Statement: [K. 417a, hasCatalogueNumberType, Köchel catalogue number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogueNumberType Context triple: [K. 417a, hasCatalogueNumberType, Köchel catalogue number]
-
A.
hasCatalogNumberSystem
chosen
Indicates that an entity uses or is associated with a particular catalog numbering system for organizing or identifying items.
-
B.
hasCatalogueNumberInDeutschCatalogue
Indicates that an entity is assigned a specific catalogue number within the Deutsch catalogue classification system.
-
C.
hasCatalogNumberPrefix
Indicates that an item’s catalog number begins with a specified prefix.
-
D.
hasOrdinalInCatalogue
Indicates that an entity is assigned a specific ordinal position or sequence number within a catalogue.
-
E.
hasBandNumber
Indicates that an entity is associated with a specific band identification number.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:17 p.m.