Triple

T15838278
Position Surface form Disambiguated ID Type / Status
Subject Danubian provinces of the Roman Empire E384037 entity
Predicate instanceOf P0 FINISHED
Object Roman provincial group C5440 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: Roman provincial group
Context triple: [Danubian provinces of the Roman Empire, instanceOf, Roman provincial group]
  • A. Roman cultural group
    A Roman cultural group is a community of people in ancient Rome and its territories who shared common language (Latin), social customs, religious practices, legal traditions, and artistic expressions that collectively defined Roman identity.
  • B. Roman province chosen
    A Roman province is an administrative territory outside the Italian peninsula governed by Rome, overseen by appointed officials, and used for taxation, resource extraction, and military control within the Roman Empire.
  • C. Roma subgroup
    A Roma subgroup is a distinct community within the broader Romani people, defined by shared ancestry, dialect, cultural practices, and often historical migration patterns.
  • D. Roman legion
    A Roman legion is a large, highly organized military unit of the ancient Roman army, typically composed of several thousand heavily armed infantry supported by cavalry and specialized troops.
  • E. ancient Roman ally
    An ancient Roman ally is a foreign individual, city, or state that entered into a formal relationship with Rome—often through treaties or agreements—providing military or political support in exchange for protection, privileges, or limited autonomy.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
Created at: April 10, 2026, 4:49 a.m.