Triple
T17081000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | national court enforcement system of China |
E414468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial enforcement system |
C38791
|
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: judicial enforcement system Context triple: [national court enforcement system of China, instanceOf, judicial enforcement system]
-
A.
judicial discipline system
A judicial discipline system is a formal framework of rules, procedures, and oversight mechanisms designed to investigate, evaluate, and sanction misconduct or ethical violations by judges to maintain integrity and public confidence in the judiciary.
-
B.
judicial crackdown
A judicial crackdown is a coordinated and often politically driven use of courts and legal processes to aggressively target, punish, or deter specific individuals, groups, or activities.
-
C.
judicial network
A judicial network is a structured system of interconnected courts, judges, and legal institutions that interact through case decisions, precedents, and administrative relationships to shape and apply the law.
-
D.
judicial administrative office
A judicial administrative office is an organizational unit within the court system responsible for managing the non-judicial functions of the judiciary, such as case processing, records management, budgeting, staffing, and overall court operations support.
-
E.
judiciary
The judiciary is the branch of government responsible for interpreting laws, resolving disputes, and ensuring justice is administered fairly and in accordance with the constitution and legal principles.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.