Triple
T19514982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troy VI |
E488254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Late Bronze Age settlement |
C42105
|
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: Late Bronze Age settlement Context triple: [Troy VI, instanceOf, Late Bronze Age settlement]
-
A.
Mycenaean settlement
A Mycenaean settlement is a Late Bronze Age Aegean habitation site characterized by fortified architecture, palatial or administrative centers, and associated domestic, economic, and ritual structures reflecting Mycenaean social and political organization.
-
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.
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.
-
D.
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.
-
E.
Greco-Roman settlement
A Greco-Roman settlement is a community or town established or influenced by ancient Greek and Roman cultures, characterized by their architectural styles, urban planning, social structures, and economic activities.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:40 p.m.