Triple

T15003077
Position Surface form Disambiguated ID Type / Status
Subject court of Constantius II E374140 entity
Predicate instanceOf P0 FINISHED
Object late Roman administrative center C19733 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: late Roman administrative center
Context triple: [court of Constantius II, instanceOf, late Roman administrative center]
  • A. Byzantine city
    A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
  • B. Roman town
    A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
  • C. late Roman diocese chosen
    A late Roman diocese was a large administrative district of the Roman Empire, grouping several provinces under the authority of a vicarius to improve governance, taxation, and imperial control.
  • D. Roman imperial residence
    A Roman imperial residence is a grand, often fortified palace complex that served as the official home, administrative center, and ceremonial stage for the Roman emperor and his court.
  • E. late Roman provincial governor
    A late Roman provincial governor was an imperial official responsible for administering a province’s civil government, justice, taxation, and local defense under the increasingly centralized and bureaucratic structures of the later 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_69d85ccc84388190aa151e5173370c8d completed April 10, 2026, 2:13 a.m.
Created at: April 10, 2026, 2:54 a.m.