Triple

T20135476
Position Surface form Disambiguated ID Type / Status
Subject Pulpudeva E491012 entity
Predicate instanceOf P0 FINISHED
Object Thracian settlement C43014 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: Thracian settlement
Context triple: [Pulpudeva, instanceOf, Thracian settlement]
  • A. Greco-Roman settlement
    A Greco-Roman settlement is a community or town established or influenced by ancient Greek and Roman cultures, characterized by their architectural styles, urban planning, social structures, and economic activities.
  • B. Thracian tribe
    A Thracian tribe is a distinct ancient ethnic and social group belonging to the broader Thracian people, typically defined by shared territory, culture, language, and political organization in the regions of Southeast Europe.
  • C. 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.
  • 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. Sarmatian people
    The Sarmatian people were an ancient Iranian-speaking nomadic group who inhabited the Eurasian steppe north of the Black Sea from around the 5th century BCE to the 4th century CE, known for their skilled cavalry and influence on neighboring cultures, including the Romans.
  • 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_69da62651a0c8190a3e05e95e056a66b completed April 11, 2026, 3:01 p.m.
Created at: April 11, 2026, 11:32 p.m.