Triple
T6247249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahler Symphony No. 2 |
E139749
|
entity |
| Predicate | revisionsUntilYear |
P18133
|
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: [Mahler Symphony No. 2, revisionsUntilYear, 1895]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisionsUntilYear Context triple: [Mahler Symphony No. 2, revisionsUntilYear, 1895]
-
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.
majorRevisionYear
chosen
Indicates the year in which a significant or primary revision of something (such as a work, document, or standard) was made.
-
D.
elevationRevisionYear
Indicates the year in which the elevation value for an entity was last revised or updated.
-
E.
redefinitionYear
Indicates the year in which something was redefined, such as when its definition, scope, or formal status was officially changed.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631f511c81908d413320efdce42e |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.