Triple

T2936329
Position Surface form Disambiguated ID Type / Status
Subject Hazor E79278 entity
Predicate instanceOf P0 FINISHED
Object Canaanite city-state C13065 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: Canaanite city-state
Context triple: [Hazor, instanceOf, Canaanite city-state]
  • A. Mesopotamian city
    A Mesopotamian city is an ancient urban settlement characterized by organized streets, monumental temples (ziggurats), centralized administration, and irrigation-based agriculture along the Tigris and Euphrates rivers.
  • B. ancient Egyptian city
    An ancient Egyptian city is an urban settlement along the Nile characterized by monumental temples and tombs, administrative and residential districts, and a society organized around pharaonic rule, religion, and agriculture.
  • C. Phoenician colony
    A Phoenician colony is a settlement established by the ancient maritime Phoenician civilization along foreign coasts for trade, resource extraction, and cultural expansion while maintaining ties to its founding city.
  • D. pre-Columbian city-state
    A pre-Columbian city-state is an autonomous urban-centered political entity in the Americas that existed before European contact, typically comprising a primary city and its surrounding territories, governed by its own ruling elite, institutions, and cultural traditions.
  • E. Yoruba city-state
    A Yoruba city-state is an autonomous urban-centered political entity historically found in southwestern Nigeria and neighboring regions, typically organized around a sacred king (oba), a complex hierarchy of chiefs, and vibrant economic, religious, and artistic institutions.
  • 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_69ad8b0fbab081908f6a61567c045d8d completed March 8, 2026, 2:43 p.m.
Created at: March 8, 2026, 2:56 p.m.