Triple
T12708054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Arsen of Serbia |
E303640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Serbian prince |
C12966
|
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: Serbian prince Context triple: [Prince Arsen of Serbia, instanceOf, Serbian prince]
-
A.
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.
-
B.
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.
-
C.
Serbian nobleman
chosen
A Serbian nobleman is a member of the historical or contemporary Serbian aristocracy, typically holding hereditary titles, land, and social privileges within Serbian society.
-
D.
Armenian prince
An Armenian prince is a nobleman of Armenia’s historical aristocracy, often ruling a principality or region and serving as a military and political leader within the Armenian kingdom or under foreign suzerainty.
-
E.
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.
- 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.