Triple
T19529373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eight Prohibitions |
E488618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gojoseon law |
C41796
|
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: Gojoseon law Context triple: [Eight Prohibitions, instanceOf, Gojoseon law]
-
A.
Chinese legal code
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.
Mongol law
Mongol law refers to the legal principles, customary practices, and codified regulations—most notably the Yassa—developed under the Mongol Empire to govern its diverse subjects, maintain military discipline, and ensure social order across vast conquered territories.
-
C.
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.
-
D.
Malacca Sultanate law code
The Malacca Sultanate law code is a historical legal framework that governed political authority, trade, social conduct, and Islamic practices in the Malacca Sultanate, serving as a foundational reference for later Malay legal traditions.
-
E.
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.
- F. None of above. chosen
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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:41 p.m.