Triple
T6070609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K2 archaeological site |
E135270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iron Age settlement |
C4488
|
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 settlement Context triple: [K2 archaeological site, instanceOf, Iron Age 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.
historical settlement
chosen
A historical settlement is a once-inhabited place of past human residence whose physical remains, records, and cultural traces provide evidence of earlier social, economic, and political life.
-
D.
Human settlement
A human settlement is a community where people live and interact, ranging in scale from small villages to large cities, characterized by organized habitation, infrastructure, and social structures.
-
E.
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.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:10 p.m.