Triple
T9933693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law of Ukraine on the National Bank of Ukraine |
E192705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian law |
C13978
|
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: Ukrainian law Context triple: [Law of Ukraine on the National Bank of Ukraine, instanceOf, Ukrainian law]
-
A.
Ukrainian legislation
chosen
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.
settlement in Ukraine
A settlement in Ukraine is a populated locality, such as a city, town, village, or rural community, officially recognized within the country’s administrative-territorial structure.
-
C.
Russian imperial law
Russian imperial law was the evolving body of statutes, decrees, and legal principles that governed the Russian Empire from the early tsarist period through 1917, reflecting autocratic authority, codified reforms, and complex interactions among imperial, regional, and customary norms.
-
D.
EU legal act
An EU legal act is a binding or non-binding instrument adopted by the European Union’s institutions—such as regulations, directives, decisions, recommendations, or opinions—to create, modify, or guide the application of law within the EU legal order.
-
E.
cabinet of Ukraine
The Cabinet of Ukraine is the highest body of executive power in Ukraine, responsible for implementing laws, managing state policy, and overseeing the operation of government ministries and agencies.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:44 p.m.