Triple
T29817953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 2 in C minor |
E757162
|
entity |
| Predicate | approximatePremiereDate |
P102528
|
FINISHED |
| Object | 1895 |
—
|
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: 1895 | Statement: [Symphony No. 2 in C minor, approximatePremiereDate, 1895]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePremiereDate Context triple: [Symphony No. 2 in C minor, approximatePremiereDate, 1895]
-
A.
approximatePremiereYear
chosen
Indicates the estimated calendar year in which something, typically a work or event, first premiered.
-
B.
revisedPremiereDate
Indicates that the originally scheduled premiere date of something has been changed to a new date.
-
C.
originallyScheduledReleaseDate
Indicates the date on which something was first planned or intended to be released, before any later changes or rescheduling.
-
D.
regularPremiereDate
Indicates the calendar date on which something (such as a show, event, or series) begins its standard or ongoing run after any initial or special premieres.
-
E.
previewReleaseDate
Indicates the date on which a preview or pre-release version of something is or was made available.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 29, 2026, 5:27 p.m.