Triple
T32299932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip III, Landgrave of Hesse-Butzbach |
E825208
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Hesse noble |
C46082
|
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: House of Hesse noble Context triple: [Philip III, Landgrave of Hesse-Butzbach, instanceOf, House of Hesse noble]
-
A.
House of Hesse and by Rhine
The House of Hesse and by Rhine was a German grand ducal dynasty that ruled the Grand Duchy of Hesse (centered on Darmstadt) from the early 19th century until the end of the German monarchies in 1918.
-
B.
House of Hesse-Kassel
The House of Hesse-Kassel was a German princely dynasty that ruled the Landgraviate (and later Electorate) of Hesse-Kassel, playing a significant political and military role in the Holy Roman Empire and later German states.
-
C.
member of the House of Hesse-Kassel
chosen
A member of the House of Hesse-Kassel is an individual belonging to the German princely dynasty that ruled the Landgraviate and later Electorate of Hesse-Kassel, a branch of the larger House of Hesse.
-
D.
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.
-
E.
House of Nassau-Dietz
The House of Nassau-Dietz was a cadet branch of the German noble House of Nassau that ruled parts of the northern Netherlands and Friesland, eventually becoming the direct ancestors of the Dutch royal House of Orange-Nassau.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:45 a.m.