Triple
T15436266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Heart Catholic Church Cootamundra |
E369770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage-listed church building |
C17995
|
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: heritage-listed church building Context triple: [Sacred Heart Catholic Church Cootamundra, instanceOf, heritage-listed church building]
-
A.
heritage-listed church
chosen
A heritage-listed church is a historically or architecturally significant place of Christian worship that has been officially recognized and protected for its cultural value.
-
B.
Historic church
A historic church is a long-standing religious building of significant architectural, cultural, and spiritual importance that reflects the beliefs, artistry, and community life of its era.
-
C.
stone church building
A stone church building is a religious structure constructed primarily from stone, typically featuring architectural elements such as a nave, altar, and often a steeple or tower for worship and community gatherings.
-
D.
Georgian church building
A Georgian church building is a Christian place of worship constructed or used during the Georgian era (1714–1830/37), typically characterized by balanced classical proportions, restrained ornamentation, and often brick or stone facades reflecting the architectural tastes of that period.
-
E.
fortified church
A fortified church is a religious building designed or modified with defensive features—such as walls, towers, and battlements—to protect its congregation and surrounding community during times of conflict.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
Created at: April 10, 2026, 3:21 a.m.