Triple
T22209035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 9 in D minor |
E548891
|
entity |
| Predicate | majorRevisionPeriod |
P147300
|
FINISHED |
| Object | 1890s |
—
|
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: 1890s | Statement: [Symphony No. 9 in D minor, majorRevisionPeriod, 1890s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRevisionPeriod Context triple: [Symphony No. 9 in D minor, majorRevisionPeriod, 1890s]
-
A.
majorRevisionYear
Indicates the year in which a significant or primary revision of something (such as a work, document, or standard) was made.
-
B.
majorRevision
Indicates a substantial change or overhaul made to something, significantly altering its previous form or content.
-
C.
majorRevisionDate
Indicates the date on which an entity underwent a significant or substantial update or revision.
-
D.
previousMajorRevisionYear
Indicates the calendar year in which the immediately preceding major revision or version of an item was released or finalized.
-
E.
numberOfMajorRevisions
Indicates the count of significant revision events that have occurred for an 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b29eb808190ab8abaa1e0e354fa |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e723f65c5c8190a0ee3c539e5d0767 |
completed | April 21, 2026, 7:15 a.m. |
Created at: April 16, 2026, 8:36 p.m.