Triple
T15395613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Dutch Church |
E368169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch colonial church |
C13684
|
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: Dutch colonial church Context triple: [Old Dutch Church, instanceOf, Dutch colonial church]
-
A.
Dutch colonial building
chosen
A Dutch colonial building is a structure characterized by steeply pitched, often gambrel roofs, symmetrical facades, and practical, modest detailing reflecting Dutch architectural traditions adapted to colonial-era environments.
-
B.
Jesuit church
A Jesuit church is a Roman Catholic church built, used, or administered by the Society of Jesus, typically characterized by Baroque or Renaissance architecture, a strong emphasis on preaching and education, and interior designs that promote clear visibility of the altar and pulpit.
-
C.
Baroque church
A Baroque church is a richly ornamented Christian worship building characterized by dramatic spatial compositions, dynamic forms, and lavish decorative elements designed to evoke emotional and spiritual awe.
-
D.
Dutch trading post
A Dutch trading post is a commercial outpost established by the Dutch, primarily during the 17th and 18th centuries, to facilitate trade, resource extraction, and colonial administration in foreign territories.
-
E.
Baroque chapel
A Baroque chapel is an ornately decorated, often small sacred space characterized by dramatic architecture, rich ornamentation, and theatrical use of light to inspire emotional religious experience.
- F. None of above.
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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.