Triple
T24411684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Maria Presentatiekerk (Ommel) |
E615466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church building in the Netherlands |
C48969
|
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 the Netherlands Context triple: [St. Maria Presentatiekerk (Ommel), instanceOf, church building in the Netherlands]
-
A.
cathedral in the Netherlands
A cathedral in the Netherlands is a large, historically significant Christian church that serves as the seat of a bishop, characterized by distinctive Dutch architectural styles and cultural heritage.
-
B.
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.
-
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.
town in the Netherlands
A town in the Netherlands is a moderately sized, locally governed urban settlement characterized by residential neighborhoods, commercial areas, public services, and cultural or historical features within Dutch territory.
-
E.
national monument of the Netherlands
A national monument of the Netherlands is a building, structure, or site officially designated and protected by the Dutch government for its exceptional cultural, historical, or architectural significance.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:09 a.m.