Triple
T14331990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vetus Urbs |
E355370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient city district |
C32966
|
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 district Context triple: [Vetus Urbs, instanceOf, ancient city district]
-
A.
ancient district
chosen
An ancient district is a historically defined administrative or geographic area that existed in antiquity, often characterized by distinct political, cultural, or social functions within a larger civilization.
-
B.
archaeological district
An archaeological district is a geographically defined area containing a significant concentration, linkage, or continuity of archaeological sites, features, or artifacts that collectively represent important historical or prehistorical activities or cultures.
-
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.
historic city quarter
A historic city quarter is an urban area characterized by preserved architecture, street patterns, and cultural landmarks that reflect the social, economic, and architectural history of a particular period.
-
E.
medieval urban district
A medieval urban district is a distinct, often walled or gated, neighborhood within a medieval town or city characterized by its specific social, economic, or administrative functions and spatial organization.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:13 a.m.