Triple
T35763483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudolf Firkušný |
E1033943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Czech emigrant to the United States |
C62588
|
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: Czech emigrant to the United States Context triple: [Rudolf Firkušný, instanceOf, Czech emigrant to the United States]
-
A.
Czech emigrant
chosen
A Czech emigrant is an individual who has left the Czech Republic to reside permanently or long-term in another country, often for economic, political, educational, or personal reasons.
-
B.
Czech emigrant to Canada
A Czech emigrant to Canada is an individual originally from the Czech Republic who has relocated to Canada, typically seeking new opportunities, stability, or a different quality of life while often maintaining cultural ties to their homeland.
-
C.
Latvian emigrant to the United States
A Latvian emigrant to the United States is an individual born in Latvia who has relocated to and established residence in the U.S., often maintaining cultural ties to Latvia while adapting to American society.
-
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.
Bohemian immigrant
A Bohemian immigrant is an individual who has relocated from the historical region of Bohemia (now part of the Czech Republic) to another country, often bringing distinct Central European cultural traditions and perspectives to their new homeland.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.