Triple
T4771991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gertrud von Hindenburg |
E105948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian aristocrat |
C12971
|
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 aristocrat Context triple: [Gertrud von Hindenburg, instanceOf, Prussian aristocrat]
-
A.
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.
-
B.
Austrian noble
An Austrian noble is a member of the historical aristocracy of Austria, typically holding hereditary titles, land, and social privileges within the Habsburg and later Austrian realms.
-
C.
member of German nobility
chosen
A member of German nobility is an individual belonging to a historically privileged social class in German-speaking regions, typically holding hereditary titles, land, and social status recognized under traditional aristocratic systems.
-
D.
Belgian aristocrat
A Belgian aristocrat is a member of Belgium’s hereditary nobility, typically bearing a noble title, upholding longstanding family traditions, and often participating in the country’s cultural, social, and sometimes political life.
-
E.
Dutch nobleman
A Dutch nobleman is a male member of the Netherlands' hereditary or titular nobility, historically holding social status, privileges, and often land or official positions within Dutch 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:21 p.m.