Triple
T6439510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ein deutsches Requiem |
E138181
|
entity |
| Predicate | firstCompletePerformanceYear |
P69183
|
FINISHED |
| Object | 1869 |
—
|
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: 1869 | Statement: [Ein deutsches Requiem, firstCompletePerformanceYear, 1869]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCompletePerformanceYear Context triple: [Ein deutsches Requiem, firstCompletePerformanceYear, 1869]
-
A.
finalPerformanceYear
Indicates the year in which an entity’s performance or activity is recorded or recognized for the last time.
-
B.
firstCompleterYear
Indicates the calendar or academic year in which an entity first completed a specified program, requirement, or activity.
-
C.
yearOfPerformance
chosen
Indicates the specific calendar year in which a performance, event, or action took place.
-
D.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
E.
originalCompletionYear
Indicates the year in which something (such as a project, work, or construction) was first fully completed.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06967241c8190965bac395adf2d03 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:45 p.m.