Triple
T27573642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warsaw Pact advisers |
E696099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military advisers |
C33723
|
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 advisers Context triple: [Warsaw Pact advisers, instanceOf, military advisers]
-
A.
Afghan military leaders
Afghan military leaders are influential figures who have commanded armed forces or factions in Afghanistan, shaping the country’s security, politics, and conflicts through their strategic, ideological, and often regional power bases.
-
B.
military involvement
chosen
Military involvement refers to the participation of a nation's armed forces in activities ranging from combat operations and peacekeeping missions to training, advisory roles, and support functions within domestic or international contexts.
-
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.
senior military advisory position
A senior military advisory position is a high-ranking role responsible for providing expert strategic, operational, and policy guidance to top government or defense leaders to inform national security decisions.
-
E.
military administration
Military administration is the organizational and managerial framework responsible for planning, directing, and overseeing the personnel, resources, logistics, and policies that enable a military force to function effectively.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:44 p.m.