Triple
T3508977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Kerensky |
E74149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prime Minister of Russia |
C10855
|
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: Prime Minister of Russia Context triple: [Alexander Kerensky, instanceOf, Prime Minister of Russia]
-
A.
President of the Russian Soviet Federative Socialist Republic
The President of the Russian Soviet Federative Socialist Republic was the head of state of the RSFSR, serving as its highest executive authority during the final period of the Soviet Union.
-
B.
Prime Minister of Poland
The Prime Minister of Poland is the head of government responsible for directing the Council of Ministers, implementing domestic and foreign policy, and overseeing the day-to-day administration of the Polish state.
-
C.
Prime Minister of France
The Prime Minister of France is the head of government responsible for directing national policy, overseeing the operation of the civil service, and coordinating the actions of the ministers under the authority of the President of the Republic.
-
D.
Soviet statesman
A Soviet statesman is a high-ranking political leader or government official in the Soviet Union responsible for shaping and implementing state policy, diplomacy, and ideological direction.
-
E.
de facto head of government
chosen
A de facto head of government is a person who, regardless of formal title or legal status, effectively exercises the primary executive authority and decision-making power within a government.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:18 p.m.