Triple
T33614055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code of Administrative Justice of the Czech Republic |
E861066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | source of law of the Czech Republic |
C26467
|
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: source of law of the Czech Republic Context triple: [Code of Administrative Justice of the Czech Republic, instanceOf, source of law of the Czech Republic]
-
A.
Czech statute
chosen
A Czech statute is a formal written law enacted by the Parliament of the Czech Republic that establishes, modifies, or regulates legal rights and obligations within the Czech legal system.
-
B.
Slovak statute
A Slovak statute is a formal written law enacted by the National Council of the Slovak Republic that regulates specific areas of public or private life within Slovakia’s legal system.
-
C.
source of civil law
A source of civil law is any authoritative origin—such as statutes, judicial decisions, customs, or legal doctrine—from which binding civil legal rules are derived and recognized within a legal system.
-
D.
Czechoslovak legal decree
A Czechoslovak legal decree is a formal, state-issued legal act or regulation that had the force of law in Czechoslovakia, typically used to implement, interpret, or modify existing legislation or policy.
-
E.
Czech lawyer
A Czech lawyer is a legal professional qualified in the Czech Republic who advises and represents clients in matters governed by Czech and European law, including civil, criminal, administrative, and commercial cases.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.