Triple

T17113539
Position Surface form Disambiguated ID Type / Status
Subject Regio I Latium et Campania E415283 entity
Predicate instanceOf P0 FINISHED
Object region of the Roman Empire C27363 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: region of the Roman Empire
Context triple: [Regio I Latium et Campania, instanceOf, region of the Roman Empire]
  • A. part of the Roman Empire chosen
    A "part of the Roman Empire" is any geographically or administratively defined region, province, or territory that was under the political control and governance of the Roman state during its historical existence.
  • B. 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.
  • C. 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.
  • D. Roman province
    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.
  • E. area of ancient Rome
    An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman civilization.
  • 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_69d886d090cc8190a39cb94992586905 completed April 10, 2026, 5:12 a.m.
Created at: April 10, 2026, 5:35 a.m.