Triple
T8937493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nizhny Novgorod Kremlin |
E212813
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic fortified complex |
C13727
|
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: historic fortified complex Context triple: [Nizhny Novgorod Kremlin, instanceOf, historic fortified complex]
-
A.
historic military fort
A historic military fort is a fortified structure or complex built in the past for defense and military operations, often preserved today as a cultural and historical landmark.
-
B.
historic coastal fort
A historic coastal fort is a fortified structure built along a shoreline to defend strategic waterways and harbors from naval threats, often featuring thick masonry walls, artillery emplacements, and commanding views of the sea.
-
C.
fortified settlement
chosen
A fortified settlement is a community enclosed by defensive structures such as walls, ramparts, or palisades, designed to protect its inhabitants and resources from external threats.
-
D.
monumental complex
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
-
E.
historic watchtower
A historic watchtower is a tall, fortified structure built in the past to provide elevated vantage points for surveillance, defense, and communication across surrounding lands or coastlines.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:58 p.m.