Triple
T35060690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Kadesh |
E1011582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Late Bronze Age city-state |
C39346
|
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 city-state Context triple: [Kingdom of Kadesh, instanceOf, Late Bronze Age city-state]
-
A.
Canaanite city-state
A Canaanite city-state is an independent, fortified urban center in ancient Canaan that controlled its surrounding territory, governed by a local ruler and integrated into regional trade, diplomacy, and warfare.
-
B.
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.
-
C.
Late Bronze Age settlement
A Late Bronze Age settlement is a community site from roughly 1550–1200 BCE characterized by domestic structures, storage and craft areas, and material culture reflecting advanced metallurgy, trade networks, and complex social organization.
-
D.
ancient urban center
chosen
An ancient urban center is a densely populated, historically significant settlement that served as a focal point for political, economic, religious, and cultural activities in early civilizations.
-
E.
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.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.