Triple
T28734070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic core of Dresden |
E730745
|
entity |
| Predicate | containsReconstructedBuilding |
P61459
|
FINISHED |
| Object | Dresden Frauenkirche |
—
|
NE NERFINISHED |
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: Dresden Frauenkirche | Statement: [historic core of Dresden, containsReconstructedBuilding, Dresden Frauenkirche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsReconstructedBuilding Context triple: [historic core of Dresden, containsReconstructedBuilding, Dresden Frauenkirche]
-
A.
reconstructedBuilding
Indicates that a building has been rebuilt or restored after damage, destruction, or significant alteration.
-
B.
containsReconstructionOf
chosen
Indicates that one entity includes or incorporates a recreated, restored, or reconstructed version of another entity.
-
C.
reconstructionBuilt
Indicates that one entity carried out or was responsible for constructing a rebuilt or restored version of another entity.
-
D.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
E.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 28, 2026, 5:59 a.m.