Triple
T25976985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergo Beria |
E645968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military engineer |
C1592
|
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 military engineer Context triple: [Sergo Beria, instanceOf, Soviet military engineer]
-
A.
Soviet naval officer
A Soviet naval officer is a commissioned member of the Soviet Navy responsible for commanding ships, submarines, or naval units, enforcing military discipline, and executing maritime operations in accordance with Soviet military doctrine and state interests.
-
B.
Russian field marshal
A Russian field marshal is the highest-ranking military officer in the Russian (historically Imperial or Soviet-equivalent) army, responsible for commanding large-scale operations and shaping overall military strategy.
-
C.
Soviet Air Defense Forces commander
A Soviet Air Defense Forces commander was a high-ranking military officer responsible for planning, directing, and coordinating the detection, interception, and destruction of hostile aerial threats within the airspace of the Soviet Union and its allies.
-
D.
Soviet scientist
chosen
A Soviet scientist is a researcher or engineer who conducted scientific or technological work within the political, ideological, and institutional framework of the Soviet Union.
-
E.
Red Army commander
A Red Army commander is a high-ranking military officer responsible for planning, directing, and overseeing Soviet armed forces operations and personnel within the Red Army.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 8:52 a.m.