Triple
T16248331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alec Coppel |
E394432
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian expatriate in the United Kingdom |
C2133
|
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: Australian expatriate in the United Kingdom Context triple: [Alec Coppel, instanceOf, Australian expatriate in the United Kingdom]
-
A.
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.
-
B.
American expatriate in the United Kingdom
An American expatriate in the United Kingdom is a U.S. citizen who resides long-term in the UK, navigating life, work, and culture within British society while maintaining ties to their American identity and legal obligations.
-
C.
Canadian emigrant to the United Kingdom
A Canadian emigrant to the United Kingdom is a person who has left Canada to reside permanently or long-term in the UK, often adapting to British society while retaining aspects of their Canadian identity.
-
D.
Australian person
chosen
An Australian person is an individual who is a citizen or resident of Australia, typically associated with its diverse multicultural society, English language use, and cultural practices influenced by Indigenous, British, and broader global traditions.
-
E.
British-born person
A British-born person is an individual whose place of birth is within the United Kingdom, typically conferring them British nationality at birth.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:04 a.m.