Triple

T29528503
Position Surface form Disambiguated ID Type / Status
Subject Allegro in B-flat major, K. 3 E749132 entity
Predicate hasKochelNumber P167005 FINISHED
Object 3 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: 3 | Statement: [Allegro in B-flat major, K. 3, hasKochelNumber, 3]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasKochelNumber
Context triple: [Allegro in B-flat major, K. 3, hasKochelNumber, 3]
  • A. hasWorkNumberInBachGesellschaft
    Indicates that an entity is assigned a specific work number in the Bach-Gesellschaft (BG) catalog of Bach’s compositions.
  • B. 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.
  • C. hasWKN
    Indicates that an entity is associated with a specific Wertpapierkennnummer (WKN), i.e., a unique German securities identification code.
  • D. hasHornbostelSachsNumber
    Indicates that an entity (typically a musical instrument) is assigned a specific Hornbostel–Sachs classification number that encodes its type and method of sound production.
  • E. hasMusicalNumberIn
    Indicates that a musical number (song or performance) appears within or is featured in a specific work, scene, or production.
  • 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_69f0bd46d99c81908ba9d01cc1dbef7d completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66c9efdfc8190b2137dc6e1685baf completed May 2, 2026, 9:29 p.m.
PD Predicate disambiguation batch_69f6633ac8a88190ab0cda62bbfcf9b0 completed May 2, 2026, 8:48 p.m.
PDg Predicate description generation batch_69f6642e676c8190af0e6b1416eed6d2 completed May 2, 2026, 8:53 p.m.
Created at: April 28, 2026, 4:49 p.m.