Triple
T6096455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passetto di Borgo |
E135889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fortified corridor |
C11519
|
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: fortified corridor Context triple: [Passetto di Borgo, instanceOf, fortified corridor]
-
A.
fortified pass
A fortified pass is a strategically important narrow route through difficult terrain that has been strengthened with defensive structures to control movement and resist enemy forces.
-
B.
fortified quarter
A fortified quarter is a heavily defended district within a settlement, protected by walls, towers, and controlled access points to safeguard key populations, resources, or institutions.
-
C.
ceremonial corridor
chosen
A ceremonial corridor is a formal, often architecturally embellished passageway designed to frame and elevate processions, rituals, or symbolic movement through a space.
-
D.
fortified building
A fortified building is a heavily constructed structure designed with defensive features such as thick walls, limited entry points, and protective battlements to resist attacks and provide security for its occupants.
-
E.
fortified tower
A fortified tower is a tall, strongly built defensive structure designed to provide elevated surveillance, protection, and control over the surrounding area.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:12 p.m.