Triple

T16186475
Position Surface form Disambiguated ID Type / Status
Subject Charter of Moscow Oblast E392817 entity
Predicate instanceOf P0 FINISHED
Object regional constitution C13681 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: regional constitution
Context triple: [Charter of Moscow Oblast, instanceOf, regional constitution]
  • A. subnational constitution chosen
    A subnational constitution is a fundamental legal document that organizes and governs a constituent unit within a federal or decentralized state—such as a province, state, or region—by defining its institutions, powers, and relationship to the national constitution.
  • B. regional legislation
    Regional legislation comprises the laws, regulations, and legal frameworks enacted by subnational authorities (such as states, provinces, or regions) to govern matters within their territorial jurisdiction.
  • C. regional assembly
    A regional assembly is a deliberative body composed of representatives from a specific geographic area that debates, formulates, and sometimes enacts policies or regulations affecting that region.
  • D. regional institutional system
    A regional institutional system is a coordinated network of organizations, rules, and practices within a specific geographic area that collectively shape governance, economic activity, and social outcomes.
  • E. oral constitution
    Oral constitution refers to a personality and behavioral pattern theorized in psychoanalytic and constitutional psychology as rooted in early oral-stage experiences, often characterized by traits such as dependency, receptivity, and a focus on ingestion or verbal expression.
  • 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_69d87f1e49ac8190a311b54d32990576 completed April 10, 2026, 4:39 a.m.
Created at: April 10, 2026, 5:02 a.m.