Triple
T17178041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guaramid dynasty |
E416911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Georgian dynasty |
C16683
|
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 dynasty Context triple: [Guaramid dynasty, instanceOf, medieval Georgian dynasty]
-
A.
medieval Georgian kingdom
A medieval Georgian kingdom is a feudal Christian monarchy in the Caucasus region characterized by fortified cities, dynastic rule, and a culture shaped by both Eastern and Western influences.
-
B.
medieval Georgian principality
chosen
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.
-
C.
medieval Bulgarian dynasty
A medieval Bulgarian dynasty is a ruling family that governed the Bulgarian state during the Middle Ages, shaping its political structure, territorial expansion, cultural development, and relations with neighboring powers.
-
D.
medieval Georgian noblewoman
A medieval Georgian noblewoman is an aristocratic woman of the Georgian kingdoms who held social status, land-related privileges, and dynastic responsibilities within the feudal and courtly structures of the Middle Ages.
-
E.
Armenian dynasty
An Armenian dynasty is a hereditary ruling family originating from Armenia that held political power and authority over Armenian territories during a specific historical period.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:37 a.m.