Triple
T35930148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law on the National Flag of Latvia |
E1039137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latvian law |
C64547
|
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: Latvian law Context triple: [Law on the National Flag of Latvia, instanceOf, Latvian law]
-
A.
Lithuanian law
Lithuanian law is the national legal system of Lithuania, based on a civil law tradition and governed by the Constitution, statutes, and subordinate legislation regulating public, private, and administrative relations within 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.
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.
-
D.
Polish law
Polish law is the national legal system of Poland, based primarily on civil law traditions, that regulates the rights, duties, and relationships of individuals, organizations, and public authorities within the Polish state.
-
E.
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.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.