Triple
T38323143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TrV 176 |
E1036710
|
entity |
| Predicate | workOpeningMotif |
P40258
|
FINISHED |
| Object | famous brass fanfare in C–G–C |
—
|
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: famous brass fanfare in C–G–C | Statement: [TrV 176, workOpeningMotif, famous brass fanfare in C–G–C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workOpeningMotif Context triple: [TrV 176, workOpeningMotif, famous brass fanfare in C–G–C]
-
A.
openingMotif
chosen
Indicates that one element serves as the initial recurring theme or pattern that introduces and sets the tone for another element, such as a work or sequence.
-
B.
openingMotifDescription
Indicates a description of the initial recurring musical or thematic idea that begins a work or section.
-
C.
openingMotive
Indicates the initial reason, trigger, or intent that prompts an action or event to begin.
-
D.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
E.
featuresMotif
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.