Triple
T13906967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigantian territory |
E334378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iron Age territory |
C34344
|
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: Iron Age territory Context triple: [Brigantian territory, instanceOf, Iron Age territory]
-
A.
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.
-
B.
Bronze Age period
The Bronze Age period is a historical era characterized by the widespread use of bronze for tools and weapons, the rise of early urban civilizations, and significant advances in trade, writing, and social complexity.
-
C.
Bronze Age subperiod
A Bronze Age subperiod is a distinct chronological phase within the broader Bronze Age, defined by characteristic developments in metallurgy, technology, society, and material culture.
-
D.
Bronze Age battle
A Bronze Age battle is an armed conflict between organized groups during the Bronze Age, typically involving bronze weapons, chariots, early fortifications, and tactics shaped by emerging complex societies.
-
E.
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.
- F. None of above. chosen
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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.