Triple

T28626827
Position Surface form Disambiguated ID Type / Status
Subject Sapinuwa E724547 entity
Predicate instanceOf P0 FINISHED
Object Hittite settlement C54346 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: Hittite settlement
Context triple: [Sapinuwa, instanceOf, Hittite settlement]
  • A. Aegean settlement
    An Aegean settlement is a community or habitation site located in the Aegean region, typically characterized by its maritime connections, regional architecture, and cultural practices tied to the ancient civilizations surrounding the Aegean Sea.
  • B. Philistine settlement
    A Philistine settlement is an archaeological and historical concept referring to a community or town established and inhabited by the Philistines, typically characterized by distinct material culture, architecture, and coastal Levantine location during the Iron Age.
  • C. Hittite institution
    A Hittite institution is an organized social, political, religious, or legal structure within Hittite society that governed behavior, administration, and cultural practices in the Hittite civilization.
  • D. 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.
  • E. Thracian settlement
    A Thracian settlement is an ancient community or habitation site established and occupied by the Thracian people, typically characterized by fortified structures, distinctive material culture, and strategic locations in the Balkans.
  • 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_69f01d822ac08190932de59ec2268ed2 completed April 28, 2026, 2:37 a.m.
Created at: April 28, 2026, 4:36 a.m.