Triple
T15961199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law on Defence of the Republic of Belarus |
E387062
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Belarusian law |
C36741
|
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: Belarusian law Context triple: [Law on Defence of the Republic of Belarus, instanceOf, Belarusian law]
-
A.
Ukrainian legislation
Ukrainian legislation is the system of legal norms, acts, and regulations adopted by competent Ukrainian authorities that govern social relations, define rights and obligations, and establish the legal framework of the state.
-
B.
Estonian law
Estonian law is the body of legal rules and principles governing the Republic of Estonia, based on a civil law system, the Constitution, and legislation enacted by the Riigikogu, supplemented by EU law and international agreements.
-
C.
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.
-
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.
Russian federal law
A Russian federal law is a legally binding normative act adopted by the Federal Assembly and signed by the President of Russia, regulating key areas of public and private life across the entire Russian Federation.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:53 a.m.