Triple
T35174685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John of Brandenburg |
E1015661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of House of Hohenzollern |
C8279
|
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 House of Hohenzollern Context triple: [John of Brandenburg, instanceOf, member of House of Hohenzollern]
-
A.
House of Hohenzollern member
chosen
A House of Hohenzollern member is an individual belonging by birth or legitimate adoption to the historic German noble and royal dynasty that ruled territories including Brandenburg-Prussia and the German Empire.
-
B.
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.
-
C.
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.
-
D.
former German prince
A former German prince is an individual who once held, but no longer possesses, a princely title within the historical German nobility, typically due to political, legal, or dynastic changes.
-
E.
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.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.