Triple
T21080192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tollund Man |
E519343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iron Age person |
C26115
|
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 person Context triple: [Tollund Man, instanceOf, Iron Age person]
-
A.
Iron Age territory
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.
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.
-
C.
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.
-
D.
Person from antiquity
chosen
A Person from antiquity is an individual who lived in ancient historical periods, typically characterized by limited written records and distinct cultural, social, and technological contexts compared to the modern era.
-
E.
Iron Age pottery
Iron Age pottery comprises ceramic vessels and artifacts produced during the Iron Age, characterized by regionally distinct forms, decorative styles, and manufacturing techniques that reflect the social, economic, and technological practices of contemporary communities.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:49 p.m.