Triple
T37280875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto I, Count of Guelders |
E925387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Wassenberg |
C66045
|
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 Wassenberg Context triple: [Otto I, Count of Guelders, instanceOf, member of the House of Wassenberg]
-
A.
member of the House of Hohenberg
A member of the House of Hohenberg is an individual belonging by birth or lawful adoption to the noble Hohenberg family, historically associated with the morganatic branch of the Habsburg dynasty.
-
B.
member of the House of Schoenaich-Carolath
A member of the House of Schoenaich-Carolath is an individual belonging by birth or lawful adoption to this historic German noble family, traditionally associated with aristocratic titles, estates, and social standing.
-
C.
member of the House of Leiningen
A member of the House of Leiningen is an individual belonging by birth or lawful adoption to the historic German noble family of Leiningen, sharing its lineage, titles, and dynastic heritage.
-
D.
member of the House of Sponheim
A member of the House of Sponheim is an individual belonging by birth or marriage to the medieval German noble dynasty that held territories primarily in the regions of present-day Rhineland-Palatinate and Carinthia.
-
E.
member of the House of Kyburg
A member of the House of Kyburg is an individual belonging to the medieval Swiss noble dynasty that held significant territorial and political power in parts of present-day Switzerland during the High Middle Ages.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.