Triple

T23007297
Position Surface form Disambiguated ID Type / Status
Subject Concerto in E major, RV 265 E572810 entity
Predicate hasRISMNumber P150621 FINISHED
Object RV 265 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: RV 265 | Statement: [Concerto in E major, RV 265, hasRISMNumber, RV 265]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRISMNumber
Context triple: [Concerto in E major, RV 265, hasRISMNumber, RV 265]
  • A. hasRISMGenre
    Indicates that an entity is associated with a musical genre classification as defined by the RISM (Répertoire International des Sources Musicales) standard.
  • 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. hasRahlfsNumber
    Indicates that an entity (typically a Septuagint manuscript or text unit) is associated with a specific Rahlfs catalog number used to identify it.
  • 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. catalogueRaisonneNumber
    Indicates the identifier assigned to a work in a catalogue raisonné, linking it to its authoritative scholarly listing.
  • 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_69e245b6a3ac81908087599eefe3e365 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1835802a881908fe817c3fa728a82 completed April 29, 2026, 4:04 a.m.
PD Predicate disambiguation batch_69ef3b9cd5488190bcd23183179f48cd completed April 27, 2026, 10:34 a.m.
PDg Predicate description generation batch_69ef538b29c081908fa56ee35a1dcee7 completed April 27, 2026, 12:16 p.m.
Created at: April 17, 2026, 3:51 p.m.