Triple
T9197942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hesse-Philippsthal-Barchfeld |
E220762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cadet branch of the House of Hesse |
C5399
|
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: cadet branch of the House of Hesse Context triple: [Hesse-Philippsthal-Barchfeld, instanceOf, cadet branch of the House of Hesse]
-
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.
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 Reuss
A member of the House of Reuss is an individual belonging to the historic German princely family that ruled various small states in Thuringia, traditionally naming all male members Heinrich (Henry).
-
D.
cadet branch
chosen
A cadet branch is a junior line of a noble or royal family descended from a younger child, typically holding lesser titles and precedence than the main line.
-
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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:25 p.m.