Triple
T30131552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Agency of Ukraine on Exclusion Zone Management |
E765858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian state agency |
C32398
|
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 state agency Context triple: [State Agency of Ukraine on Exclusion Zone Management, instanceOf, Ukrainian state agency]
-
A.
Ukrainian government body
chosen
A Ukrainian government body is an official public institution established by the state of Ukraine to exercise specific executive, legislative, judicial, or administrative functions in accordance with national law.
-
B.
Belarusian government agency
A Belarusian government agency is an official public institution established by the state of Belarus to implement specific governmental functions, policies, and administrative tasks within its designated area of responsibility.
-
C.
government agency of Russia
A government agency of Russia is an official state body established by the Russian Federation to implement public policy, administer specific functions, and provide services within a defined area of governance under federal or regional authority.
-
D.
Russian federal agency
A Russian federal agency is a government body established by the Russian Federation to implement federal laws, execute state policies, and manage specific administrative functions across the country.
-
E.
government agency of Poland
A government agency of Poland is an official public institution established by the Polish state to perform specific administrative, regulatory, or service functions on behalf of the government.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:15 p.m.