Triple

T2929756
Position Surface form Disambiguated ID Type / Status
Subject Germania E78932 entity
Predicate instanceOf P0 FINISHED
Object Roman provincial designation 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 designation
Context triple: [Germania, instanceOf, Roman provincial designation]
  • A. 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.
  • B. ancient Roman title
    An ancient Roman title is a formal designation or rank used in Roman society and government to denote an individual's official role, status, or authority within the political, military, religious, or social hierarchy.
  • C. Roman town
    A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
  • D. province of the Byzantine Empire
    A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
  • E. client state of the Roman Empire
    A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
  • 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_69ad8b0d40b481908bc2a5fa2e73c3fb completed March 8, 2026, 2:43 p.m.
Created at: March 8, 2026, 2:55 p.m.