Triple
T23063353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concerto in A minor, RV 356 |
E574965
|
entity |
| Predicate | frequentlyUsedFor |
P144936
|
FINISHED |
| Object | violin pedagogy |
—
|
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: violin pedagogy | Statement: [Concerto in A minor, RV 356, frequentlyUsedFor, violin pedagogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentlyUsedFor Context triple: [Concerto in A minor, RV 356, frequentlyUsedFor, violin pedagogy]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
-
C.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
D.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
E.
frequentUseCase
chosen
Indicates a situation, scenario, or pattern of use that occurs regularly or more often than others in relation to the subject.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a1f49c81909db7e0473ec2bb1b |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.