Triple
T7623382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aschwin zur Lippe-Biesterfeld |
E172556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Lippe |
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: member of the House of Lippe Context triple: [Aschwin zur Lippe-Biesterfeld, instanceOf, member of the House of Lippe]
-
A.
member of the House of Hesse-Darmstadt
A member of the House of Hesse-Darmstadt is an individual belonging by birth or marriage to the German princely dynasty that historically ruled the Landgraviate and later Grand Duchy of Hesse-Darmstadt.
-
B.
member of the House of Welf
A member of the House of Welf is an individual belonging by birth or legitimate adoption to the historic European noble dynasty known as the Welfs, which has produced numerous dukes, princes, and monarchs.
-
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.
member of the House of Württemberg
A member of the House of Württemberg is an individual belonging by birth or lawful adoption to the historic German noble and royal dynasty that ruled the region of Württemberg and its predecessor territories.
-
E.
member of the House of Solms
A member of the House of Solms is an individual belonging by birth or lawful adoption to the historic German noble family of Solms, sharing its lineage, titles, and dynastic heritage.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:56 p.m.