Triple
T21969842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig Leichhardt |
E542557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian person |
C21339
|
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 person Context triple: [Ludwig Leichhardt, instanceOf, Prussian person]
-
A.
person from the Kingdom of Prussia
chosen
A person from the Kingdom of Prussia is an individual who lived in or held citizenship of the historical German state of Prussia during its existence as a kingdom (1701–1918), shaped by its distinct political, cultural, and social institutions.
-
B.
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.
-
C.
Prussian royal
A Prussian royal is a member of the ruling Hohenzollern dynasty or its close relatives who held hereditary titles and exercised or symbolized monarchical authority in the Kingdom of Prussia.
-
D.
East German person
An East German person is an individual who lived in or originated from the former German Democratic Republic (GDR), shaped by its socialist political system, culture, and historical context prior to German reunification.
-
E.
Prussian noblewoman
A Prussian noblewoman is an aristocratic woman from the historical Kingdom of Prussia, typically characterized by her high social rank, landowning family background, and adherence to the conservative, militaristic, and courtly traditions of Prussian society.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:02 p.m.