Triple
T11212139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venta Belgarum |
E265334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romano-British settlement |
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: Romano-British settlement Context triple: [Venta Belgarum, instanceOf, Romano-British settlement]
-
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.
Celtic settlement
A Celtic settlement is a community or habitation site established by Celtic peoples, typically characterized by fortified hilltops, roundhouses, and a material culture reflecting Celtic social, economic, and religious practices.
-
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.
Iron Age site
An Iron Age site is an archaeological location containing material remains, features, and structures dating to the period when iron became the dominant material for tools and weapons, typically characterized by specific regional cultural, technological, and settlement patterns.
-
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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:30 p.m.