Triple
T34199562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of K2 |
E877336
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early Iron Age polity |
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: early Iron Age polity Context triple: [Kingdom of K2, instanceOf, early Iron Age polity]
-
A.
Iron Age territory
chosen
An Iron Age territory is a geographically defined area controlled by a community or polity during the Iron Age, characterized by shared cultural practices, political organization, and economic activities.
-
B.
sub-Roman polity
A sub-Roman polity is a regional political entity that emerged in former Western Roman territories, blending residual Roman institutions with local or incoming non-Roman power structures during the transitional period after imperial collapse.
-
C.
Early Bronze Age settlement
An Early Bronze Age settlement is a permanent or semi-permanent community dating to the early phase of the Bronze Age, characterized by emerging social complexity, metalworking, and distinctive architectural and material culture remains.
-
D.
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.
-
E.
Bronze Age civilization sphere
A Bronze Age civilization sphere is a geographically and culturally connected region in which societies shared and exchanged technologies, trade networks, and social practices centered around the production and use of bronze.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:55 a.m.