Triple
T8683519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurandukht (Cuman princess) |
E206095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Georgian royal consort |
C3879
|
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 Georgian royal consort Context triple: [Gurandukht (Cuman princess), instanceOf, medieval Georgian royal consort]
-
A.
royal consort
chosen
A royal consort is the spouse of a reigning monarch who holds a recognized position at court, often with ceremonial duties but typically without sovereign authority.
-
B.
Georgian prince
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.
Georgian monarch
A Georgian monarch is a sovereign ruler of the Kingdom of Georgia or its successor Georgian realms, holding supreme political and symbolic authority over the state and its people.
-
D.
medieval Georgian principality
A medieval Georgian principality is a semi-autonomous territorial domain within the historical Kingdom of Georgia, ruled by a local prince or noble dynasty that exercised regional political, military, and economic authority while recognizing the suzerainty of a higher Georgian monarch or overlord.
-
E.
prince consort
A prince consort is the husband of a reigning queen who holds the title of prince rather than king and typically has no sovereign authority.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.