Triple
T22836137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aron |
E565952
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Bulgarian nobility |
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: member of the Bulgarian nobility Context triple: [Aron, instanceOf, member of the Bulgarian nobility]
-
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.
member of the Georgian nobility
A member of the Georgian nobility is an individual belonging to the hereditary aristocratic class of Georgia, historically endowed with land, titles, and social privileges within the Georgian feudal and royal systems.
-
C.
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.
-
D.
member of the Burgundian nobility
A member of the Burgundian nobility is an individual belonging to the hereditary aristocratic elite of the historical Duchy or County of Burgundy, holding land, titles, and social privileges within its feudal hierarchy.
-
E.
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.
- 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.