Triple
T12708057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Arsen of Serbia |
E303640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Karađorđević dynasty |
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 Karađorđević dynasty Context triple: [Prince Arsen of Serbia, instanceOf, member of the Karađorđević dynasty]
-
A.
member of the House of Karađorđević
chosen
A member of the House of Karađorđević is an individual belonging by birth or lawful adoption to the Serbian royal dynasty that historically ruled Serbia and later the Kingdom of Serbs, Croats, and Slovenes (Yugoslavia).
-
B.
House of Karađorđević
The House of Karađorđević is a Serbian royal dynasty that ruled Serbia and later the Kingdom of Serbs, Croats and Slovenes (Yugoslavia), playing a central role in the region’s 19th- and 20th-century political history.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:23 p.m.