Triple
T17563537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poggio del Telegrafo fortifications |
E427751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient defensive 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: ancient defensive complex Context triple: [Poggio del Telegrafo fortifications, instanceOf, ancient defensive complex]
-
A.
military fortification system
A military fortification system is an integrated network of defensive structures, obstacles, and support facilities designed to protect territory, forces, and strategic assets from enemy attack.
-
B.
ancient building complex
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
-
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.
inner fortification complex
The inner fortification complex is a heavily defended core area within a larger fortified site, containing critical structures and defenses that protect the most vital personnel, resources, and command functions.
-
E.
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.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.