Triple
T35319541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinand von Quast |
E1019999
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian official |
C62194
|
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: Prussian official Context triple: [Ferdinand von Quast, instanceOf, Prussian official]
-
A.
Bavarian civil servant
A Bavarian civil servant is a public-sector employee working within the administrative, legal, or regulatory institutions of the Free State of Bavaria, responsible for implementing laws, delivering public services, and upholding regional and federal regulations.
-
B.
Prussian statesman
A Prussian statesman is a political leader or high-ranking government official from the Kingdom of Prussia who shaped its domestic policies, diplomacy, and military strategy, often influencing broader European affairs.
-
C.
Prussian prince
A Prussian prince is a male royal family member of the Kingdom of Prussia, typically holding hereditary titles, political influence, and social prestige within the Prussian and broader German nobility.
-
D.
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.
-
E.
Prussian noble
A Prussian noble is a member of the historically privileged landowning and military aristocracy of the Kingdom of Prussia, characterized by hereditary titles, large estates, and significant influence in governance and the officer corps.
- F. None of above. chosen
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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.