Triple
T1679815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscovy |
E36313
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian principality |
C9058
|
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: Russian principality Context triple: [Muscovy, instanceOf, Russian principality]
-
A.
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).
-
B.
oblast of Russia
An oblast of Russia is a primary administrative division comparable to a province, governed by regional authorities under the federal structure of the Russian Federation.
-
C.
republic of Russia
The Republic of Russia is a conceptual class representing a sovereign, federated state characterized by a republican form of government, centralized authority, and a diverse composition of regions and peoples within its political and legal framework.
-
D.
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.
-
E.
constituent entity of Russia
A constituent entity of Russia is a primary administrative-territorial unit of the Russian Federation, such as a republic, krai, oblast, city of federal significance, autonomous okrug, or autonomous oblast, that possesses a defined degree of political and administrative autonomy under federal law.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:29 p.m.