Triple
T33524821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altstadt (Dresden) |
E858608
|
entity |
| Predicate | FrauenkircheReconstructionCompleted |
P47627
|
FINISHED |
| Object | 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: 2005 | Statement: [Altstadt (Dresden), FrauenkircheReconstructionCompleted, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrauenkircheReconstructionCompleted Context triple: [Altstadt (Dresden), FrauenkircheReconstructionCompleted, 2005]
-
A.
hasReconstructedChurch
Indicates that an entity has rebuilt or restored a church, typically after damage, destruction, or disuse.
-
B.
churchConstructionCompleted
chosen
Indicates that the process of building or constructing a church has been finished.
-
C.
reconstructedBuilding
Indicates that a building has been rebuilt or restored after damage, destruction, or significant alteration.
-
D.
originalChurchDestroyed
Indicates that the initially established church building was demolished or ceased to exist, typically due to destruction rather than relocation or replacement.
-
E.
mainChurchBuilt
Indicates that the primary church associated with an entity was constructed or established at a particular time or by a particular agent.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.