Triple
T20603359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porta Borsari |
E506238
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman city gate |
C24216
|
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 Roman city gate Context triple: [Porta Borsari, instanceOf, ancient Roman city gate]
-
A.
ancient city gate
chosen
An ancient city gate is a monumental architectural structure that controlled access to a fortified settlement, often serving defensive, ceremonial, and administrative functions.
-
B.
medieval city gate
A medieval city gate is a fortified architectural structure that controls access to a walled town or city, combining defensive features like towers and portcullises with symbolic and administrative functions.
-
C.
ancient Roman monument
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
-
D.
ancient Roman structure
An ancient Roman structure is a man-made construction from the Roman civilization, such as temples, amphitheaters, aqueducts, or baths, characterized by advanced engineering, arches, and durable materials like stone and concrete.
-
E.
Roman Agora entrance
The Roman Agora entrance is the monumental gateway that provided access to the ancient Roman marketplace, often marked by grand columns, inscriptions, and architectural details reflecting the civic and commercial importance of the space.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:41 a.m.