Triple
T25122448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish higher education law |
E629301
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish law |
C49752
|
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: Polish law Context triple: [Polish higher education law, instanceOf, Polish law]
-
A.
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.
-
B.
Belarusian law
Belarusian law is the system of legal norms and institutions governing social relations in Belarus, shaped by its constitution, legislation, presidential decrees, and influences from both Soviet legal traditions and contemporary international law.
-
C.
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.
-
D.
Romanian law
Romanian law is the national legal system of Romania, based primarily on civil law traditions, that regulates the rights, obligations, and interactions of individuals, organizations, and public authorities within the Romanian state.
-
E.
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.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:28 a.m.