Triple
T8520475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 2 in G minor, Op. 22 |
E201681
|
entity |
| Predicate | revisionYears |
P18133
|
FINISHED |
| Object | 1835–1838 |
—
|
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: 1835–1838 | Statement: [Piano Sonata No. 2 in G minor, Op. 22, revisionYears, 1835–1838]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisionYears Context triple: [Piano Sonata No. 2 in G minor, Op. 22, revisionYears, 1835–1838]
-
A.
dateRevisionYear
Indicates the calendar year in which a particular date entry or record was revised or updated.
-
B.
reversionYear
Indicates the year in which something returns to a previous state, condition, or ownership.
-
C.
yearOfReference
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
-
D.
majorRevisionYear
chosen
Indicates the year in which a significant or primary revision of something (such as a work, document, or standard) was made.
-
E.
yearDescribedAs
Indicates the specific year in which something was formally characterized, documented, or described.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe628f8c48190a35201f9fde605cc |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.