Triple
T16546487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspectorate of Engineers of the Russian Empire |
E401955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military-technical authority |
C37607
|
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: military-technical authority Context triple: [Inspectorate of Engineers of the Russian Empire, instanceOf, military-technical authority]
-
A.
military inspection authority
A military inspection authority is an official body or designated entity responsible for examining, evaluating, and ensuring compliance with standards, regulations, and readiness requirements within armed forces units and facilities.
-
B.
military establishment
A military establishment is an organized institution or network of institutions responsible for a nation's armed forces, defense policies, and related political, economic, and social interests.
-
C.
military political organ
A military political organ is an institutional body within the armed forces responsible for overseeing political education, ideological control, and party or state loyalty among military personnel.
-
D.
military sector
The military sector encompasses organizations, resources, and activities dedicated to national defense, security operations, and the development and deployment of armed forces and related technologies.
-
E.
military capability area
A military capability area is a distinct domain of military functions, resources, and competencies grouped together to achieve specific defense and operational objectives.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:15 a.m.