Triple
T9123688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosimushchestvo |
E218920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal agency of Russia |
C7798
|
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: federal agency of Russia Context triple: [Rosimushchestvo, instanceOf, federal agency of Russia]
-
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.
Russian federal agency
chosen
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.
-
C.
federal agency of Germany
A federal agency of Germany is a governmental body operating at the national level, responsible for implementing federal laws, policies, and administrative tasks within its designated area of competence.
-
D.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
E.
United States federal government agency
A United States federal government agency is an organization established by federal law or executive authority to implement, administer, and enforce specific national policies, programs, and regulations on behalf of the U.S. 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:17 p.m.