Triple
T29146942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent (early post-Roman phase) |
E738798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sub-Roman British region |
C53486
|
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: sub-Roman British region Context triple: [Kent (early post-Roman phase), instanceOf, sub-Roman British region]
-
A.
early medieval Brittonic kingdom
chosen
An early medieval Brittonic kingdom is a politically organized territory in post-Roman Britain ruled by Brittonic-speaking elites, characterized by localized kingship, warrior aristocracies, and a fusion of Roman, Celtic, and emerging Christian traditions.
-
B.
Celtic tribal territory
A Celtic tribal territory is a geographically defined region inhabited and controlled by a specific Celtic tribe, characterized by shared cultural practices, social structures, and political organization.
-
C.
Anglo-Saxon kingdom
An Anglo-Saxon kingdom is a political entity established in early medieval England by Germanic peoples, characterized by its own monarchy, territorial domain, legal customs, and social hierarchy prior to the Norman Conquest.
-
D.
Pictish kingdom
The Pictish kingdom was an early medieval confederation of tribal societies in what is now northern and eastern Scotland, known for its distinctive symbol stones, warrior culture, and eventual unification with the Gaelic Scots.
-
E.
Anglo-Saxon town
An Anglo-Saxon town is a small, early medieval English settlement characterized by wooden buildings, a central marketplace or meeting place, and a community structured around agriculture, trade, and local governance.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:40 a.m.