Triple
T20377239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etruscan city walls of Perugia |
E497724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient city walls |
C27632
|
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 city walls Context triple: [Etruscan city walls of Perugia, instanceOf, ancient city walls]
-
A.
medieval city wall
A medieval city wall is a fortified defensive structure encircling a town or city, typically built of stone with towers, gates, and battlements to protect inhabitants from external threats.
-
B.
ancient city gate
An ancient city gate is a monumental architectural structure that controlled access to a fortified settlement, often serving defensive, ceremonial, and administrative functions.
-
C.
ancient ruined city
An ancient ruined city is a long-abandoned urban settlement whose remaining structures, artifacts, and landscape features reveal the remnants of a once-thriving civilization now decayed by time and nature.
-
D.
ancient structure
chosen
An ancient structure is a man-made construction from antiquity, such as temples, fortifications, or monuments, that reflects the architectural techniques, cultural values, and historical context of its originating civilization.
-
E.
ancient building
An ancient building is a historically significant structure from antiquity, often characterized by enduring construction materials, distinctive architectural styles, and cultural or archaeological importance.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:27 a.m.