Triple
T21939939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of Arms Act of Estonia |
E541790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Estonian national law |
C28498
|
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: Estonian national law Context triple: [Coat of Arms Act of Estonia, instanceOf, Estonian national law]
-
A.
Estonian law
chosen
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.
-
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.
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.
Danish law
Danish law is the national legal system of Denmark, based on a civil law tradition with strong welfare-state principles, comprehensive statutory regulation, and adherence to international and EU legal obligations.
-
E.
Swedish law
Swedish law is the body of legal rules and principles governing Sweden, encompassing its constitution, legislation, case law, and administrative regulations that regulate public and private life within the country.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:55 p.m.