Triple

T23649584
Position Surface form Disambiguated ID Type / Status
Subject Cenabum E584131 entity
Predicate instanceOf P0 FINISHED
Object Gallic settlement C6354 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: Gallic settlement
Context triple: [Cenabum, instanceOf, Gallic settlement]
  • A. Celtic settlement chosen
    A Celtic settlement is a community or habitation site established by Celtic peoples, typically characterized by fortified hilltops, roundhouses, and a material culture reflecting Celtic social, economic, and religious practices.
  • B. Ligurian settlement
    A Ligurian settlement is a historically or archaeologically identified inhabited place established or predominantly occupied by the ancient Ligurian people, characterized by their distinct cultural, social, and territorial attributes.
  • C. ancient Gallic tribe
    An ancient Gallic tribe is a historical Celtic-speaking community that inhabited regions of Gaul, characterized by shared cultural practices, social structures, and territorial identity prior to and during Roman expansion.
  • D. Numidian settlement
    A Numidian settlement is a community or town established by the ancient Numidian people of North Africa, typically characterized by fortified hilltop locations, mixed pastoral-agricultural economies, and cultural influences from both indigenous Berber traditions and Mediterranean civilizations.
  • 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.

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_69e248fefafc81909656921192f30e80 completed April 17, 2026, 2:51 p.m.
Created at: April 17, 2026, 6:49 p.m.