Triple
T25583340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radko Dimitriev |
E641312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bulgarian emigrant to the Russian Empire |
C50484
|
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: Bulgarian emigrant to the Russian Empire Context triple: [Radko Dimitriev, instanceOf, Bulgarian emigrant to the Russian Empire]
-
A.
Dutch emigrant to the Russian Empire
A Dutch emigrant to the Russian Empire is an individual originating from the Netherlands who permanently relocated to and settled within the territories of the Russian Empire.
-
B.
Russian emigrant to the United Kingdom
A Russian emigrant to the United Kingdom is an individual born and raised in Russia who has relocated to the UK to reside there long-term or permanently, often for reasons such as work, study, family, or political circumstances.
-
C.
Russian émigré
A Russian émigré is a person who has left Russia to live permanently in another country, often due to political, social, or economic reasons.
-
D.
Russian emigrant to the United States
A Russian emigrant to the United States is an individual who leaves Russia to reside permanently or long-term in the U.S., navigating cultural, social, and legal transitions between the two countries.
-
E.
British emigrant to the Soviet Union
A British emigrant to the Soviet Union is an individual originally from Britain who relocated to and settled in the Soviet Union, often for political, ideological, professional, or personal reasons.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:14 p.m.