Triple
T36802553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Jewish Law in Hungary |
E909359
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian statute |
C32764
|
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: Hungarian statute Context triple: [First Jewish Law in Hungary, instanceOf, Hungarian statute]
-
A.
Hungarian law
chosen
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.
-
B.
Austro-Hungarian law
Austro-Hungarian law refers to the complex, dual legal system and body of statutes, regulations, and judicial practices that governed the Austro-Hungarian Empire from its formation in 1867 until its dissolution in 1918, balancing shared imperial competencies with distinct Austrian and Hungarian legal frameworks.
-
C.
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.
-
D.
Hungarian legal work
Hungarian legal work encompasses the professional activities of legal practitioners in Hungary, including advising clients, drafting documents, and representing parties in matters governed by Hungarian law.
-
E.
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.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.