Triple
T9308044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustan 14 regions of Rome |
E223936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban district system |
C19533
|
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: urban district system Context triple: [Augustan 14 regions of Rome, instanceOf, urban district system]
-
A.
urban administrative area
chosen
An urban administrative area is a geographically defined part of a city or town governed by specific local authorities responsible for public services, regulation, and planning within its boundaries.
-
B.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
C.
urban service area
An urban service area is a designated geographic zone within or around a city where public services and infrastructure—such as water, sewer, transportation, and emergency response—are planned, provided, and managed in a coordinated manner.
-
D.
urban district gateway
An urban district gateway is a prominent physical or symbolic entry point that marks the transition into a distinct city district, shaping first impressions and aiding orientation and identity.
-
E.
urban-type settlement
An urban-type settlement is a semi-urban locality that exhibits some characteristics of a town or small city—such as concentrated housing, infrastructure, and non-agricultural employment—without meeting all the criteria for full city status.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:37 p.m.