Triple
T11998912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander, Crown Prince of Yugoslavia |
E285604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Karađorđević |
C29881
|
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 Karađorđević Context triple: [Alexander, Crown Prince of Yugoslavia, instanceOf, member of the House of Karađorđević]
-
A.
member of the House of Savoy
A member of the House of Savoy is an individual belonging by birth or marriage to the historic European royal dynasty that ruled territories including Savoy, Sardinia, and eventually unified Italy.
-
B.
member of the House of Bourbon
A member of the House of Bourbon is an individual belonging by birth or legitimate descent to the historic European royal dynasty that ruled or influenced several kingdoms, including France, Spain, and Naples.
-
C.
House of Habsburg member
A House of Habsburg member is an individual belonging by birth or marriage to the historic European royal dynasty that ruled vast territories including Austria, Spain, and the Holy Roman Empire.
-
D.
member of the House of Romanov
A member of the House of Romanov is an individual belonging by birth or marriage to the former imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
-
E.
member of the Babenberg dynasty
A member of the Babenberg dynasty is an individual belonging to the medieval noble family that ruled Austria and parts of Central Europe from the 10th to the mid-13th century.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:46 p.m.