Triple
T10551221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustoritum |
E248950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman settlement in Gaul |
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: Roman settlement in Gaul Context triple: [Augustoritum, instanceOf, Roman settlement in Gaul]
-
A.
Roman settlement
A Roman settlement is a community established under Roman rule, characterized by Roman architecture, infrastructure, administration, and cultural practices integrated with local traditions.
-
B.
Roman frontier
The Roman frontier was the shifting boundary zone of the Roman Empire, marked by fortifications, military roads, and garrisoned settlements that controlled movement, trade, and defense between Roman territories and neighboring peoples.
-
C.
Roman military camp
A Roman military camp is a temporary or permanent fortified encampment laid out in a standardized, highly organized grid pattern to house, protect, and support Roman troops during campaigns.
-
D.
Numidian settlement
A Numidian settlement is a community or town established by the ancient Numidian people of North Africa, typically characterized by fortified hilltop locations, mixed pastoral-agricultural economies, and cultural influences from both indigenous Berber traditions and Mediterranean civilizations.
-
E.
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.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:34 p.m.