Triple

T31146944
Position Surface form Disambiguated ID Type / Status
Subject Regio XIV Transtiberim E793950 entity
Predicate instanceOf P0 FINISHED
Object ancient administrative region of Rome C54400 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: ancient administrative region of Rome
Context triple: [Regio XIV Transtiberim, instanceOf, ancient administrative region of Rome]
  • A. 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.
  • B. Roman regio chosen
    A Roman regio was an administrative district or region within ancient Rome or its territories, used for organizing governance, census, and urban planning.
  • C. part of the Roman Empire
    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.
  • D. 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.
  • E. 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.
  • 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_69f224d41bb48190a5621cd1485e3a30 completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 9:06 p.m.