Triple
T23063351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concerto in A minor, RV 356 |
E574965
|
entity |
| Predicate | virtuosicWritingFor |
P150826
|
FINISHED |
| Object | solo violin |
—
|
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: solo violin | Statement: [Concerto in A minor, RV 356, virtuosicWritingFor, solo violin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virtuosicWritingFor Context triple: [Concerto in A minor, RV 356, virtuosicWritingFor, solo violin]
-
A.
creativeLanguage
Indicates that an entity uses language in an original, imaginative, or non-literal way to express ideas.
-
B.
writingPartner
Indicates a collaborative relationship in which two or more entities work together as co-authors or co-writers on written material.
-
C.
writingTool
Indicates that one entity serves as a tool or instrument used by another entity for the act of writing.
-
D.
writingComponent
Indicates that one entity is a written part or element that contributes to the composition or structure of another entity.
-
E.
writingModel
Indicates that one entity serves as the writing system, script, or notation model used to represent the language or written content of another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:55 p.m.