Triple
T624496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erivan Governorate |
E14586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governorate of the Russian Empire |
C1640
|
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: governorate of the Russian Empire Context triple: [Erivan Governorate, instanceOf, governorate of the Russian Empire]
-
A.
governorate
chosen
A governorate is an administrative division of a country, typically governed by an appointed or elected official who oversees local governance and public services within its territory.
-
B.
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.
-
C.
federal city of Russia
A federal city of Russia is a major urban locality that functions as a separate federal subject, holding the same administrative status as a region or republic and typically serving as a key political, economic, or cultural center.
-
D.
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.
-
E.
Russian imperial law
Russian imperial law was the evolving body of statutes, decrees, and legal principles that governed the Russian Empire from the early tsarist period through 1917, reflecting autocratic authority, codified reforms, and complex interactions among imperial, regional, and customary norms.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.