Triple
T20095844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexei Kirillovich Vronsky |
E496397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian cavalry officer |
C30787
|
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: Russian cavalry officer Context triple: [Alexei Kirillovich Vronsky, instanceOf, Russian cavalry officer]
-
A.
Imperial Russian Army general
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 prince
A Russian prince is a male noble of princely rank in Russia, historically belonging to the aristocratic ruling class and often holding political, military, or territorial authority within the Russian Empire or its predecessor states.
-
C.
European officer
chosen
A European officer is a military or colonial administrative figure originating from a European nation, typically holding a position of authority and responsibility within an organized armed force or governing structure.
-
D.
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.
-
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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:25 p.m.