Triple
T16893076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John I, Margrave of Brandenburg |
E424223
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Ascania member |
C37187
|
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 Ascania member Context triple: [John I, Margrave of Brandenburg, instanceOf, House of Ascania member]
-
A.
member of the House of Ascania
chosen
A member of the House of Ascania is an individual belonging to the medieval German noble dynasty that ruled various principalities and territories, including Anhalt and Brandenburg, across several centuries.
-
B.
member of the House of Mecklenburg-Schwerin
A member of the House of Mecklenburg-Schwerin is an individual belonging by birth or lawful adoption to the historic German ducal and later grand ducal dynasty that ruled the territory of Mecklenburg-Schwerin.
-
C.
House of Lorraine member
A House of Lorraine member is an individual belonging by birth or legitimate descent to the historic European noble dynasty that ruled Lorraine and later provided emperors, kings, and consorts to several major monarchies.
-
D.
member of the House of Wettin
A member of the House of Wettin is an individual belonging to the historic German noble and royal dynasty that ruled various central European territories, including Saxony and Poland, over many centuries.
-
E.
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).
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:29 a.m.