Triple
T945785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagestan |
E20410
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constituent entity of the Russian Federation |
C737
|
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: constituent entity of the Russian Federation Context triple: [Dagestan, instanceOf, constituent entity of the Russian Federation]
-
A.
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.
-
B.
constituent country
A constituent country is a semi-autonomous nation within a larger sovereign state, possessing its own government and identity while sharing overarching sovereignty and institutions with the parent state.
-
C.
federal city of Russia
chosen
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.
sovereign state
A sovereign state is a politically organized territory with a permanent population, defined borders, a government, and full independent authority over its internal and external affairs.
-
E.
union republic
A union republic is a constituent political unit within a federal or quasi-federal state, typically possessing its own government and constitution while remaining subordinate to the overarching union 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:40 p.m.