Triple
T35675542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic Law on the Judiciary |
E1030845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austro-Hungarian law |
C63809
|
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: Austro-Hungarian law Context triple: [Basic Law on the Judiciary, instanceOf, Austro-Hungarian law]
-
A.
Prussian law
Prussian law refers to the body of legal principles, statutes, and judicial practices that governed the Kingdom of Prussia, characterized by a strong centralized authority, codification efforts like the Allgemeines Landrecht, and an emphasis on bureaucratic administration and social order.
-
B.
Hungarian law
Hungarian law is the legal system of Hungary, based on a civil law tradition that combines codified statutes, constitutional principles, and European Union legal norms to regulate public, private, and criminal matters within the country.
-
C.
Austrian federal law
Austrian federal law is the body of legal norms enacted at the national level in Austria that governs matters within the competence of the federal state, such as constitutional structure, civil and criminal law, and nationwide administrative regulations.
-
D.
Croatian statute
A Croatian statute is a formal written law enacted by the Croatian Parliament (Sabor) that regulates specific areas of public or private life within the Republic of Croatia’s legal system.
-
E.
Czech statute
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.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.