Triple
T19615694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Caprices for Solo Violin, Op. 1 |
E470853
|
entity |
| Predicate | compositionEndApprox |
P81904
|
FINISHED |
| Object | c. 1817 |
—
|
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: c. 1817 | Statement: [24 Caprices for Solo Violin, Op. 1, compositionEndApprox, c. 1817]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionEndApprox Context triple: [24 Caprices for Solo Violin, Op. 1, compositionEndApprox, c. 1817]
-
A.
compositionEndTime
chosen
Indicates the point in time at which a composition or creative work is considered to have been completed.
-
B.
compositionCompleted
Indicates that the process of composing or creating something (such as a work, document, or piece) has been fully completed.
-
C.
representationEnded
Indicates that a previously ongoing representation or acting-on-behalf-of relationship between entities has come to an end.
-
D.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
E.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640cf418081909d69d5bd9c479fed |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.