Triple
T10558317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedford Square |
E249147
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Georgian square |
C20568
|
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 square Context triple: [Bedford Square, instanceOf, Georgian square]
-
A.
Georgian building
chosen
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.
-
B.
Renaissance square
A Renaissance square is a public urban space characterized by harmonious proportions, classical architectural elements, and a central role in civic, commercial, and cultural life during the Renaissance period.
-
C.
Georgian inscription
A Georgian inscription is a text carved, written, or otherwise rendered in the Georgian script, typically found on monuments, buildings, artifacts, or manuscripts, conveying historical, religious, or commemorative information.
-
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.
Georgian family
A Georgian family is a close-knit household typically spanning multiple generations, characterized by strong traditions, deep respect for elders, and warm hospitality rooted in Georgian culture.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:35 p.m.