Triple
T9308045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustan 14 regions of Rome |
E223936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical territorial organization |
C12509
|
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: historical territorial organization Context triple: [Augustan 14 regions of Rome, instanceOf, historical territorial organization]
-
A.
historical polities
Historical polities are organized political entities or governing structures that existed in the past, such as kingdoms, empires, city-states, and federations, defined by their territorial control, institutions, and sociopolitical systems.
-
B.
history of a region
A history of a region is a structured account of the social, political, economic, and cultural developments that have shaped a specific geographic area over time.
-
C.
historical geographic entity
chosen
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
D.
colonial political organization
A colonial political organization is a governing structure imposed by a foreign power to administer, control, and exploit a colonized territory and its population, often subordinating local institutions and interests to imperial objectives.
-
E.
territorial state
A territorial state is a political entity that exercises sovereign authority over a clearly defined geographic area and the population within its borders.
- 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.