Triple
T8567353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarinet Concerto |
E202837
|
entity |
| Predicate | hasCadenza |
P83683
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Clarinet Concerto, hasCadenza, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCadenza Context triple: [Clarinet Concerto, hasCadenza, yes]
-
A.
hasCadenzaBy
Indicates that something (typically a musical work or passage) includes or is associated with a cadenza composed or authored by a specified entity.
-
B.
hasOrnamentation
Indicates that an entity possesses decorative features or embellishments applied to its surface or structure.
-
C.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
D.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
E.
usesChordChangesOf
Indicates that one musical work employs the same or substantially similar chord progression as another work.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d5d4ac8190a4d74c88b872d0b7 |
completed | March 31, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:20 p.m.