Triple
T15043501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St James Church, Sydney |
E379163
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Georgian-style church |
C2213
|
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: Georgian-style church Context triple: [St James Church, Sydney, instanceOf, Georgian-style church]
-
A.
Georgian church building
chosen
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.
-
B.
Gothic Revival church
A Gothic Revival church is a Christian worship building designed in the 19th-century revival of medieval Gothic architecture, featuring pointed arches, ribbed vaults, and ornate tracery.
-
C.
Georgian Orthodox church building
A Georgian Orthodox church building is a Christian worship structure associated with the Georgian Orthodox Church, typically featuring traditional Georgian ecclesiastical architecture, iconography, and liturgical spaces.
-
D.
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.
-
E.
Georgian building
A Georgian building is a structure designed in the architectural style prevalent from the early 18th to early 19th centuries, characterized by symmetry, proportion, and classical details such as sash windows, decorative cornices, and brick or stone facades.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3 a.m.