Triple
T38569700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Peter’s Church (Sankt Peders Kirke) |
E929230
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church building in Denmark |
C64771
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: church building in Denmark Context triple: [St. Peter’s Church (Sankt Peders Kirke), instanceOf, church building in Denmark]
-
A.
church building in Poland
A church building in Poland is a religious structure, typically Christian, designed for worship, liturgical ceremonies, and community gatherings, reflecting Polish historical, cultural, and architectural traditions.
-
B.
church building in the Netherlands
A church building in the Netherlands is a religious structure, often historically significant and architecturally distinctive, used for Christian worship and community activities within Dutch cultural and urban landscapes.
-
C.
church building in Germany
A church building in Germany is a religious structure, often historically and architecturally significant, designed for Christian worship and community gatherings within the German cultural and legal context.
-
D.
church building in Belgium
A church building in Belgium is a religious structure, typically Christian, located within Belgian territory and used primarily for worship, religious ceremonies, and related community activities.
-
E.
Lutheran church building
A Lutheran church building is a Christian worship structure designed and used by a Lutheran congregation, typically featuring a simple, scripture-focused interior that reflects Lutheran theological and liturgical traditions.
- F. None of above. chosen
Provenance (1 batch)
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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.