Triple
T32379820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Serge Obolensky |
E827383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tsarist military officer |
C37608
|
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: Tsarist military officer Context triple: [Prince Serge Obolensky, instanceOf, Tsarist military officer]
-
A.
Imperial Russian Army general
chosen
An Imperial Russian Army general is a high-ranking military officer of the Russian Empire responsible for commanding large formations, planning and directing operations, and implementing imperial military policy.
-
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.
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.
-
D.
Austro-Hungarian military officer
An Austro-Hungarian military officer was a commissioned leader in the armed forces of the Austro-Hungarian Empire, responsible for commanding troops, implementing imperial military policy, and upholding the dual monarchy’s authority across its diverse territories.
-
E.
Bavarian military officer
A Bavarian military officer is a commissioned leader from the historical Kingdom or modern state of Bavaria, responsible for commanding troops, executing military strategy, and upholding regional and national defense duties within the broader German armed forces context.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:51 a.m.