Triple
T7669262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | defensive complex of Saint Petersburg |
E173705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical monument ensemble |
C4549
|
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: historical monument ensemble Context triple: [defensive complex of Saint Petersburg, instanceOf, historical monument ensemble]
-
A.
cultural heritage monument
A cultural heritage monument is a historically, artistically, or culturally significant structure or site that embodies the identity, memory, and values of a community or civilization and is preserved for present and future generations.
-
B.
group of historic sites
chosen
A group of historic sites is a collection of geographically or thematically related locations that hold recognized cultural, architectural, or historical significance and are often managed or interpreted as a unified whole.
-
C.
architectural ensemble
An architectural ensemble is a coherent group of buildings and spaces designed or evolved together to form a unified, contextually integrated spatial and aesthetic whole.
-
D.
palace and park ensemble
A palace and park ensemble is a unified architectural and landscape complex where a grand residence is integrated with designed gardens, water features, and surrounding grounds to form a cohesive cultural and aesthetic whole.
-
E.
historic monument
A historic monument is a significant structure, site, or object preserved for its cultural, architectural, or historical importance, symbolizing and commemorating events, people, or eras of the past.
- 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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4 p.m.