Triple
T15268580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maragondon Church |
E364961
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish colonial stone church |
C28955
|
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: Spanish colonial stone church Context triple: [Maragondon Church, instanceOf, Spanish colonial stone church]
-
A.
Spanish Colonial adobe church
A Spanish Colonial adobe church is a religious structure characterized by thick earthen walls, simple rectilinear forms, and modest ornamentation that blend indigenous building techniques with Spanish ecclesiastical design.
-
B.
Spanish Colonial style building
chosen
A Spanish Colonial style building is characterized by its stucco walls, red clay tile roofs, arched openings, and simple, symmetrical forms often arranged around courtyards.
-
C.
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.
-
D.
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.
-
E.
Baroque monastery
A Baroque monastery is a religious complex characterized by dramatic, ornate architecture, rich decorative programs, and spatial designs intended to inspire awe and spiritual contemplation in accordance with Baroque artistic principles.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:14 a.m.