Triple
T8334788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frauenkirche (Dresden) |
E195160
|
entity |
| Predicate | reconsecrationDate |
P3370
|
FINISHED |
| Object | 30 October 2005 |
—
|
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: 30 October 2005 | Statement: [Frauenkirche (Dresden), reconsecrationDate, 30 October 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconsecrationDate Context triple: [Frauenkirche (Dresden), reconsecrationDate, 30 October 2005]
-
A.
consecrationDate
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
-
B.
rededicationDate
chosen
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
-
C.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
D.
reburialDate
Indicates the date on which something that was previously buried is buried again.
-
E.
canonizationDate
Indicates the date on which an individual was officially declared a saint (canonized) by a religious authority.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd2ca648190991e398ba70caf8d |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:57 p.m.