Triple
T26690332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippo Regius |
E672860
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Roman colony |
C5442
|
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: former Roman colony Context triple: [Hippo Regius, instanceOf, former Roman colony]
-
A.
Roman province
A Roman province is an administrative territory outside the Italian peninsula governed by Rome, overseen by appointed officials, and used for taxation, resource extraction, and military control within the Roman Empire.
-
B.
Roman town
chosen
A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
-
C.
part of the Roman Empire
A "part of the Roman Empire" is any geographically or administratively defined region, province, or territory that was under the political control and governance of the Roman state during its historical existence.
-
D.
ancient Roman ally
An ancient Roman ally is a foreign individual, city, or state that entered into a formal relationship with Rome—often through treaties or agreements—providing military or political support in exchange for protection, privileges, or limited autonomy.
-
E.
core territory of the Roman Empire
The core territory of the Roman Empire comprises the Italian peninsula and the western-central Mediterranean heartlands that formed the political, economic, and cultural center of Roman power and administration.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:25 a.m.