Triple
T8623541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian civil aviation authorities |
E204227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government agency group |
C3952
|
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: government agency group Context triple: [Russian civil aviation authorities, instanceOf, government agency group]
-
A.
group of government ministries
A group of government ministries is a coordinated collection of specialized administrative departments, each responsible for a particular policy area, that together implement and manage a government's public functions and services.
-
B.
governmental organization
chosen
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
C.
government agency division
A government agency division is a specialized organizational unit within a larger government agency that focuses on a specific set of functions, programs, or policy areas to support the agency’s overall mission.
-
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.
government committee
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.