Triple
T13581261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Crimea |
E324421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous republic of Ukraine |
C25746
|
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: autonomous republic of Ukraine Context triple: [Republic of Crimea, instanceOf, autonomous republic of Ukraine]
-
A.
former raion of Ukraine
A former raion of Ukraine is an administrative district that existed as a second-level territorial unit within Ukraine’s regional structure but was later dissolved or reorganized, typically due to administrative reforms.
-
B.
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.
-
C.
autonomous oblast
chosen
An autonomous oblast is a type of administrative division within a country that possesses a degree of self-governance and cultural or political autonomy, typically established to recognize and accommodate a specific ethnic or regional group.
-
D.
autonomous okrug of Russia
An autonomous okrug of Russia is a type of federal subject with a degree of self-governance, typically established in areas with significant indigenous or ethnic minority populations and often administratively associated with a larger region or krai.
-
E.
raion of Ukraine
A raion of Ukraine is an administrative district within an oblast that serves as a second-level territorial unit for local governance and administration.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:48 p.m.