Triple
T9889768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qin law code |
E181423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Chinese legal code |
C23617
|
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: ancient Chinese legal code Context triple: [Qin law code, instanceOf, ancient Chinese legal code]
-
A.
Chinese legal code
chosen
A Chinese legal code is a systematically organized collection of laws and regulations that defines legal norms, rights, obligations, and penalties within a Chinese jurisdiction.
-
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.
ancient Chinese state
An ancient Chinese state is a historically documented political entity that existed within the territory of what is now China, characterized by its own ruling house, administrative system, culture, and military, and interacting with neighboring states through warfare, diplomacy, and trade.
-
D.
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.
-
E.
part of the Corpus Juris Civilis
A part of the Corpus Juris Civilis is a distinct component (such as the Code, Digest, Institutes, or Novels) of the comprehensive body of Roman civil law compiled under Emperor Justinian I.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 8:39 p.m.