Triple

T30162892
Position Surface form Disambiguated ID Type / Status
Subject Flaminia et Picenum E766715 entity
Predicate instanceOf P0 FINISHED
Object Roman administrative province 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 administrative province
Context triple: [Flaminia et Picenum, instanceOf, Roman administrative province]
  • 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. 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.
  • 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. 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. 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.
  • 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_69f2247a968881909d79c18f2bfcb275 completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 7:22 p.m.