Triple

T31438019
Position Surface form Disambiguated ID Type / Status
Subject Aemilia et Liguria E801987 entity
Predicate instanceOf P0 FINISHED
Object imperial Roman administrative unit C56457 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: imperial Roman administrative unit
Context triple: [Aemilia et Liguria, instanceOf, imperial Roman administrative unit]
  • 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
    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 territorial unit chosen
    A Roman territorial unit is an administrative division of land within the Roman state, defined for purposes such as governance, taxation, military organization, and legal jurisdiction.
  • D. 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.
  • E. 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.
  • 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_69f348c475348190bf579ca858eec77c completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 9:03 p.m.