Triple
T19150461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mihailo Obrenović III |
E468791
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prince of Serbia |
C41187
|
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: Prince of Serbia Context triple: [Mihailo Obrenović III, instanceOf, Prince of Serbia]
-
A.
Grand Prince of Serbia
The Grand Prince of Serbia was the medieval ruler who held supreme political and military authority over the Serbian lands before the establishment of the Serbian kingdom.
-
B.
King of Serbia
The King of Serbia was the hereditary monarch and head of state of the Kingdom of Serbia, embodying national sovereignty and overseeing the country's governance until its integration into larger South Slavic states.
-
C.
Yugoslav prince
A Yugoslav prince is a male member of the royal family of the former Kingdom of Yugoslavia, typically holding hereditary titles and roles within the monarchy’s dynastic and ceremonial traditions.
-
D.
Prince of Bulgaria
A Prince of Bulgaria is a male royal titleholder, typically a son or close male relative of the reigning Bulgarian monarch, who holds a defined place in the line of succession and represents the Bulgarian royal family in ceremonial and dynastic roles.
-
E.
King of Yugoslavia
The King of Yugoslavia was the hereditary monarch and head of state of the Kingdom of Yugoslavia, symbolizing national unity and holding supreme authority within its constitutional framework.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:06 p.m.