Triple
T15975821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Staff of the Armed Forces of Belarus |
E387441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Belarusian government agency |
C36772
|
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: Belarusian government agency Context triple: [General Staff of the Armed Forces of Belarus, instanceOf, Belarusian government agency]
-
A.
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.
-
B.
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.
-
C.
Ukrainian government body
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.
-
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.
Romanian government agency
A Romanian government agency is a public institution established by the Romanian state to implement specific policies, deliver public services, and regulate activities within its designated area of responsibility.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:54 a.m.