Triple
T9371430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tornike Eristavi |
E225538
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Georgian nobleman |
C23495
|
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: Georgian nobleman Context triple: [Tornike Eristavi, instanceOf, Georgian nobleman]
-
A.
Finnish nobleman
A Finnish nobleman is a male member of Finland’s historical nobility, typically holding hereditary titles, land, and social status recognized under the Swedish and later Russian rule, and often involved in military, administrative, or political leadership.
-
B.
Georgian prince
chosen
A Georgian prince is a male member of the royal or noble families of Georgia, historically holding hereditary titles, political influence, and social prestige within the Georgian monarchy and aristocracy.
-
C.
Baltic German noble
A Baltic German noble was a member of the German-speaking hereditary elite in the Baltic provinces (primarily present-day Estonia and Latvia), historically holding significant land, political power, and cultural influence under various ruling empires.
-
D.
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.
-
E.
Finnish noble
A Finnish noble is a member of the historical aristocratic class in Finland, traditionally holding hereditary titles, land, and social privileges recognized by the Swedish and later Russian crowns, and organized through institutions such as the Finnish House of Nobility.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:43 p.m.