Triple
T36178268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldene Waage |
E1046636
|
entity |
| Predicate | reconstructionPhase |
P22906
|
FINISHED |
| Object | Dom-Römer redevelopment |
—
|
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: Dom-Römer redevelopment | Statement: [Goldene Waage, reconstructionPhase, Dom-Römer redevelopment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstructionPhase Context triple: [Goldene Waage, reconstructionPhase, Dom-Römer redevelopment]
-
A.
reconstructionFor
chosen
Indicates that one entity serves as a reconstruction, restoration, or rebuilt version of another entity.
-
B.
reconstructedDuring
Indicates that an entity was rebuilt, restored, or significantly repaired within a specified time period or event.
-
C.
reconstructionFeature
Indicates that one entity serves as a feature, component, or characteristic used in the reconstruction or restoration of another entity.
-
D.
reconstructionStart
Indicates the point in time or event at which a reconstruction process or activity begins.
-
E.
reconstructionBuilt
Indicates that one entity carried out or was responsible for constructing a rebuilt or restored version of another entity.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.