Triple
T22808084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law on Currency in Circulation |
E564593
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Moldovan law |
C46851
|
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: Moldovan law Context triple: [Law on Currency in Circulation, instanceOf, Moldovan law]
-
A.
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.
-
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.
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.
-
D.
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.
-
E.
district of Moldova
A district of Moldova is an administrative territorial unit within the country, typically comprising multiple towns and villages and governed by a local public authority responsible for regional administration and services.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:32 p.m.