Triple

T29021160
Position Surface form Disambiguated ID Type / Status
Subject Gaul and Britain E737454 entity
Predicate instanceOf P0 FINISHED
Object Roman imperial administrative region 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 imperial administrative region
Context triple: [Gaul and Britain, instanceOf, Roman imperial administrative region]
  • A. Roman administrative district
    A Roman administrative district is a territorial unit governed by Roman officials for the purposes of taxation, legal jurisdiction, military organization, and local administration within the Roman state.
  • 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. Roman regio
    A Roman regio was an administrative district or region within ancient Rome or its territories, used for organizing governance, census, and urban planning.
  • D. core territory of the Roman Empire
    The core territory of the Roman Empire comprises the Italian peninsula and the western-central Mediterranean heartlands that formed the political, economic, and cultural center of Roman power and administration.
  • E. administrative district of the Holy Roman Empire
    An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
  • 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_69f077ee19f881909af48f9cab00a2e5 completed April 28, 2026, 9:03 a.m.
Created at: April 28, 2026, 9:49 a.m.