Triple
T26134909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Military Council of the Republic |
E659351
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supreme military authority |
C51154
|
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: supreme military authority Context triple: [Revolutionary Military Council of the Republic, instanceOf, supreme military authority]
-
A.
Commander-in-chief
The Commander-in-chief is the highest-ranking authority responsible for the overall command, strategic direction, and ultimate decision-making of a nation's armed forces.
-
B.
supreme military rank
A supreme military rank is the highest possible position in a nation's armed forces hierarchy, typically held by a single individual with ultimate authority over all military operations and strategy.
-
C.
Allied military authority
An Allied military authority is a governing body established by cooperating allied nations' armed forces to administer, control, and coordinate military and sometimes civil affairs in occupied or liberated territories during and immediately after conflict.
-
D.
nuclear command authority
Nuclear command authority is the centralized system of legal, political, and military structures and procedures that control the authorization, decision-making, and execution of a state’s nuclear weapons use.
-
E.
supreme state authority
The supreme state authority is the highest governing body or institution within a state that holds ultimate legal and political power to make, interpret, and enforce binding decisions over its territory and population.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 8:17 p.m.