Triple
T38377730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimir Bonch-Bruyevich |
E893671
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet administrator |
C7438
|
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: Soviet administrator Context triple: [Vladimir Bonch-Bruyevich, instanceOf, Soviet administrator]
-
A.
Soviet statesman
chosen
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.
-
B.
KGB chairman
The KGB chairman is the highest-ranking official overseeing the Soviet Union’s state security and intelligence agency, responsible for directing espionage, counterintelligence, internal security, and political repression operations.
-
C.
Soviet expert
A Soviet expert is a specialist with deep knowledge of the political, economic, social, and historical aspects of the Soviet Union and its influence on global affairs.
-
D.
Soviet administrative structure
The Soviet administrative structure was a highly centralized, hierarchical system of governance in which the Communist Party controlled state institutions, economic planning, and regional authorities through overlapping layers of bureaucratic and political oversight.
-
E.
Soviet scholar
A Soviet scholar is an academic or intellectual who conducted research, teaching, or theoretical work within the ideological, institutional, and political framework of the Soviet Union.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.