Triple
T24995664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almaz Central Design Bureau |
E625560
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian state enterprise |
C25651
|
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: Russian state enterprise Context triple: [Almaz Central Design Bureau, instanceOf, Russian state enterprise]
-
A.
Russian company
A Russian company is a legally registered business entity operating within the Russian Federation’s jurisdiction, subject to its corporate, tax, and regulatory frameworks.
-
B.
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.
-
C.
organization based in Russia
chosen
An organization based in Russia is any structured group or entity—such as a company, nonprofit, institution, or association—whose primary operations, legal registration, or headquarters are located within the Russian Federation.
-
D.
Russian state
The Russian state is a centralized political entity that exercises sovereign authority over the territory and population of Russia through its institutions of governance, law, security, and administration.
-
E.
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.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:04 a.m.