Triple
T32359111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Military Council of the RSFSR |
E826811
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governmental military council |
C308
|
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: governmental military council Context triple: [Revolutionary Military Council of the RSFSR, instanceOf, governmental military council]
-
A.
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.
-
B.
military government function
A military government function is an activity or responsibility carried out by armed forces to administer, control, or support governance and public order, especially in times of conflict, occupation, or emergency.
-
C.
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.
-
D.
governing council
chosen
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
E.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:49 a.m.