Triple
T4771907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Hindenburg |
E105946
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German noble family name |
C12987
|
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: German noble family name Context triple: [von Hindenburg, instanceOf, German noble family name]
-
A.
surname of German origin
chosen
A surname of German origin is a family name derived from the German language and cultural or geographic roots within German-speaking regions.
-
B.
German noble
A German noble is a member of the historical aristocratic class in German-speaking regions, traditionally holding hereditary titles, land, and social privileges within the feudal and later monarchical systems.
-
C.
German princely dynasty
A German princely dynasty is a hereditary ruling family from the German-speaking regions of Europe that historically held princely titles, governed territories, and played significant roles in regional and imperial politics.
-
D.
Latin family name
A Latin family name is a hereditary surname of Latin origin, often derived from personal names, occupations, locations, or characteristic traits, used to identify and distinguish members of a family lineage.
-
E.
member of German nobility
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.
- 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.