Triple

T25094972
Position Surface form Disambiguated ID Type / Status
Subject St Paul’s Suite E628561 entity
Predicate inTonalSystem P106245 FINISHED
Object tonal 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: tonal | Statement: [St Paul’s Suite, inTonalSystem, tonal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inTonalSystem
Context triple: [St Paul’s Suite, inTonalSystem, tonal]
  • A. tonalSystem
    Indicates a relationship where a language or musical system is characterized by a specific set of tonal patterns or pitch distinctions that structure its sounds or expressions.
  • B. tonalArchitecture
    Indicates a relationship where one entity defines, shapes, or organizes the tonal structure or harmonic framework of another (such as a piece, passage, or system).
  • C. tonalCenter
    Indicates that one musical element functions as the primary pitch or key center around which another musical element is organized.
  • D. inTonality chosen
    Indicates that something (such as a musical element, passage, or piece) is expressed, structured, or interpreted within a specific musical key or tonal framework.
  • E. hasTuningDivision
    Indicates that one entity specifies or uses a particular system or scheme for dividing a range (such as a musical interval or scale) into tuning units.
  • 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_69e2ff2f58e881908340527bc5d34f07 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f464b8893c81909fd77666ba04feec completed May 1, 2026, 8:30 a.m.
PD Predicate disambiguation batch_69f442c861188190967655c6d8012380 completed May 1, 2026, 6:06 a.m.
Created at: April 18, 2026, 6:24 a.m.