Triple
T36368652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemens family |
E895693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German industrial dynasty |
C5114
|
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 industrial dynasty Context triple: [Siemens family, instanceOf, German industrial dynasty]
-
A.
German industrialist
chosen
A German industrialist is a business leader or entrepreneur from Germany who owns, manages, or significantly influences large-scale industrial enterprises and their economic and social impact.
-
B.
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.
-
C.
Finnish industrial family
A Finnish industrial family is a multigenerational household or lineage in Finland whose primary identity, wealth, and social influence are rooted in owning, managing, or significantly shaping industrial enterprises.
-
D.
German noble family branch
A German noble family branch is a distinct lineage or subdivision of a larger aristocratic house in German-speaking regions, typically defined by shared ancestry, territorial holdings, and hereditary titles.
-
E.
Prussian aristocratic family
A Prussian aristocratic family is a noble lineage rooted in the historical Kingdom of Prussia, characterized by hereditary titles, landed estates, military and bureaucratic service, and adherence to traditional social hierarchies and customs.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.