Triple
T16107756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esther Szekeres |
E390783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian emigrant to Australia |
C28174
|
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: Hungarian emigrant to Australia Context triple: [Esther Szekeres, instanceOf, Hungarian emigrant to Australia]
-
A.
Hungarian emigrant
chosen
A Hungarian emigrant is a person who leaves Hungary to reside permanently or long-term in another country, often for economic, political, or personal reasons.
-
B.
Hungarian emigrant to Italy
A Hungarian emigrant to Italy is an individual born or raised in Hungary who has relocated to Italy to live, work, study, or settle there, often navigating and blending Hungarian and Italian cultural, social, and legal contexts.
-
C.
British emigrant to Australia
A British emigrant to Australia is an individual who leaves the United Kingdom to settle permanently or long-term in Australia, often seeking new opportunities, lifestyle changes, or family reunification.
-
D.
Hungarian-British person
A Hungarian-British person is an individual who holds cultural, familial, or national ties to both Hungary and the United Kingdom, often embodying a blend of Hungarian and British heritage, identity, and traditions.
-
E.
Polish emigrant to the United Kingdom
A Polish emigrant to the United Kingdom is an individual born and raised in Poland who has relocated to the UK, typically for reasons such as employment, education, family reunification, or improved living conditions, and who navigates life between Polish cultural roots and British society.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5 a.m.