Triple
T21584776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Assembly Act of South Korea |
E532619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Korean law |
C27474
|
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: South Korean law Context triple: [National Assembly Act of South Korea, instanceOf, South Korean law]
-
A.
South Korean statute
chosen
A South Korean statute is a formal written law enacted by the National Assembly of South Korea that establishes binding legal rules and standards within the country’s jurisdiction.
-
B.
Gojoseon law
Gojoseon law refers to the earliest known legal system of ancient Korea’s Gojoseon kingdom, traditionally exemplified by the “Eight Prohibitions,” which regulated social order through strict penalties on crimes such as murder, theft, and adultery.
-
C.
Joseon dynasty law code
A Joseon dynasty law code is a comprehensive legal compilation that systematically codifies the administrative, civil, and criminal laws governing the Korean Joseon state and its Confucian social order.
-
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.
Kazakhstan law
Kazakhstan law is the body of legal norms, principles, and regulations governing social relations, rights, and obligations within the Republic of Kazakhstan, established by its constitution, legislation, and judicial practice.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:31 p.m.