Triple
T37956544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John XI, Wild- and Rhinegrave of Salm-Kyrburg |
E946881
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Salm |
C66177
|
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 Salm Context triple: [John XI, Wild- and Rhinegrave of Salm-Kyrburg, instanceOf, member of the House of Salm]
-
A.
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.
-
B.
member of the House of Hesse-Kassel
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.
-
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.
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.
member of the House of Hanau
A member of the House of Hanau is an individual belonging by birth or legitimate lineage to the historical German noble family that ruled the County of Hanau and its territories.
- F. None of above. chosen
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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.