Triple
T13952899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transfiguration Cathedral (Zhytomyr) |
E335575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Architectural landmark |
C28775
|
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: Architectural landmark Context triple: [Transfiguration Cathedral (Zhytomyr), instanceOf, Architectural landmark]
-
A.
architecturally significant building
chosen
An architecturally significant building is a structure whose design, innovation, historical importance, or cultural impact distinguishes it as notably influential or exemplary within the built environment.
-
B.
architectural district
An architectural district is a geographically defined area characterized by a concentration of buildings and structures that share significant architectural styles, historical periods, or design features, often protected or managed for their cultural and aesthetic value.
-
C.
Historic site
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
D.
urban landmark
An urban landmark is a prominent, easily recognizable feature within a city—such as a building, monument, or natural formation—that serves as a visual reference point and symbol of the area’s identity.
-
E.
Historical building type
A historical building type is a category of structures defined by shared architectural features, construction methods, and cultural functions characteristic of a specific historical period or tradition.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.