Triple

T8174760
Position Surface form Disambiguated ID Type / Status
Subject Qing Code E190913 entity
Predicate instanceOf P0 FINISHED
Object imperial law code C3883 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 law code
Context triple: [Qing Code, instanceOf, imperial law code]
  • A. Byzantine law code
    A Byzantine law code is a systematically organized collection of legal rules, imperial edicts, and judicial interpretations that governed civil, criminal, and ecclesiastical matters in the Byzantine Empire.
  • B. ancient Near Eastern law collection
    An ancient Near Eastern law collection is a compiled set of legal rules, case decisions, and royal decrees from early civilizations such as Mesopotamia, intended to articulate social norms, regulate behavior, and legitimize authority.
  • C. late Roman legal codex
    A late Roman legal codex is a formally compiled, systematically organized collection of imperial laws, juristic writings, and legal principles produced in the later Roman Empire to standardize and preserve authoritative legal practice.
  • D. Japanese imperial law
    Japanese imperial law is the body of legal principles, statutes, and institutional practices that governed the authority, succession, and functions of the Emperor and imperial household within Japan’s historical and constitutional frameworks.
  • E. imperial edict chosen
    An imperial edict is a formal, authoritative decree issued by an emperor that carries the force of supreme law within an 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_69ca82c1c0a08190bf8692b4d91a03ca completed March 30, 2026, 2:03 p.m.
Created at: March 30, 2026, 5:40 p.m.