Triple
T29455532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transcaucasian Commissariat |
E747088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government of Transcaucasia |
C55630
|
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: government of Transcaucasia Context triple: [Transcaucasian Commissariat, instanceOf, government of Transcaucasia]
-
A.
North Caucasian state
A North Caucasian state is a political entity located in the North Caucasus region, typically characterized by its diverse ethnic composition, strategic position between Europe and Asia, and complex historical and geopolitical dynamics.
-
B.
Caucasian Albania
Caucasian Albania was an ancient kingdom and later province in the eastern Caucasus, roughly corresponding to parts of modern Azerbaijan and southern Dagestan, known from classical and early medieval sources.
-
C.
Abkhaz historical region
An Abkhaz historical region is a geographically defined area traditionally inhabited or governed by Abkhaz people, characterized by its distinct historical, cultural, and political development within the broader Caucasus context.
-
D.
West Ukrainian People's Republic
The West Ukrainian People's Republic was a short-lived, self-proclaimed Ukrainian state established in Eastern Galicia in 1918 following the collapse of the Austro-Hungarian Empire, which sought independence before being incorporated into Poland.
-
E.
District of Tbilisi
A District of Tbilisi is an administrative subdivision of the city that manages local governance, public services, and community infrastructure within its defined urban area.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:36 p.m.