Triple
T1852258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Galicia–Volhynia |
E41621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval East Slavic state |
C8750
|
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 East Slavic state Context triple: [Kingdom of Galicia–Volhynia, instanceOf, medieval East Slavic state]
-
A.
vassal state
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
-
B.
institution of the Kingdom of Hungary
An institution of the Kingdom of Hungary is an organized body or establishment—political, legal, religious, educational, or administrative—that operated within and under the authority of the historical Kingdom of Hungary.
-
C.
Crusader state
A Crusader state is a feudal polity established by Western European crusaders in the Eastern Mediterranean and surrounding regions during the medieval Crusades, maintained through military, religious, and political control over conquered territories.
-
D.
oblast of the Russian Empire
An oblast of the Russian Empire was an administrative-territorial unit, typically on the empire’s periphery, governed by appointed officials and possessing a lower status than a governorate (guberniya).
-
E.
constituent republic of the Soviet Union
A constituent republic of the Soviet Union was a nominally sovereign national republic that, while having its own government and constitution, was politically and economically subordinate to the central Soviet federal authority.
- F. None of above. chosen
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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:33 p.m.