Triple
T32218251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gozzurg |
E822991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval complex |
C10580
|
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: medieval complex Context triple: [Gozzurg, instanceOf, medieval complex]
-
A.
medieval castle
A medieval castle is a fortified stone stronghold featuring defensive walls, towers, and a keep, designed to protect its inhabitants and assert the power of its lord.
-
B.
medieval city
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
-
C.
medieval capital
A medieval capital is the carved topmost element of a column or pillar in Middle Ages architecture, often richly decorated with foliage, figures, or symbolic motifs to transition between the shaft and the structure it supports.
-
D.
medieval civilization
A medieval civilization is a complex society that flourished roughly between the 5th and 15th centuries, characterized by feudal social structures, agrarian economies, religious dominance (often by the Church), fortified settlements, and evolving political institutions that laid foundations for the modern state.
-
E.
monumental complex
chosen
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.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:38 a.m.