Triple
T22836105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikola, count of Sredets |
E565951
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Bulgarian nobleman |
C31436
|
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: medieval Bulgarian nobleman Context triple: [Nikola, count of Sredets, instanceOf, medieval Bulgarian nobleman]
-
A.
Bulgarian noble
chosen
A Bulgarian noble is a member of the historical aristocratic class in Bulgaria, holding hereditary titles, land, and political influence within the medieval or early modern Bulgarian state.
-
B.
medieval Bulgarian noblewoman
A medieval Bulgarian noblewoman is an aristocratic female member of Bulgarian society during the Middle Ages, typically associated with landownership, political influence, and participation in courtly and religious life.
-
C.
Serbian nobleman
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.
Bulgarian nobles
Bulgarian nobles are members of the historical aristocratic class in Bulgaria who held hereditary titles, land, and political influence, shaping the country’s medieval and early modern governance, culture, and military affairs.
-
E.
medieval European noble
A medieval European noble is a high-ranking member of the feudal aristocracy who holds land granted by a monarch in exchange for military service and governance over vassals and peasants.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:35 p.m.