Triple
T12012437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | String Quartet No. 15 in A minor, Op. 132 |
E285933
|
entity |
| Predicate | usesFugato |
P60129
|
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: [String Quartet No. 15 in A minor, Op. 132, usesFugato, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFugato Context triple: [String Quartet No. 15 in A minor, Op. 132, usesFugato, yes]
-
A.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
B.
hasGuitarEffect
Indicates that one entity applies, uses, or is associated with a particular guitar effect in relation to another entity.
-
C.
usesMusicalElement
chosen
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
-
D.
usesAutoTune
Indicates that the subject employs automatic pitch-correction technology (Auto-Tune) on their vocal or audio recordings.
-
E.
usesMusicalSystem
Indicates that one entity employs or operates according to a particular musical system, framework, or set of musical rules.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d7777481908cd5a001f75e2ee3 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.