Triple
T16202734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georg Baring |
E393244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hanoverian 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: Hanoverian officer Context triple: [Georg Baring, instanceOf, Hanoverian officer]
-
A.
Prussian general
A Prussian general is a high-ranking military officer of the historical Kingdom of Prussia, characterized by rigorous discipline, strategic planning, and leadership in organizing and commanding armies in war.
-
B.
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.
-
C.
German Army general
A German Army general is a high-ranking military officer responsible for leading large army formations, developing operational strategies, and overseeing the training, discipline, and effectiveness of subordinate units within the German land forces.
-
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.
military officer
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:03 a.m.