Triple
T19468846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troy II |
E487068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bronze Age settlement layer |
C25299
|
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: Bronze Age settlement layer Context triple: [Troy II, instanceOf, Bronze Age settlement layer]
-
A.
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.
-
B.
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.
-
C.
Bronze Age period
chosen
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.
Yayoi-period settlement
A Yayoi-period settlement is an archaeological site representing a community from Japan’s Yayoi era (c. 300 BCE–300 CE), typically characterized by paddy fields, pit dwellings, storage facilities, and material evidence of early wet-rice agriculture and social stratification.
-
E.
Bronze Age subperiod
A Bronze Age subperiod is a distinct chronological phase within the broader Bronze Age, defined by characteristic developments in metallurgy, technology, society, and material culture.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.