Triple
T32399759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Iranians |
E827910
|
entity |
| Predicate | immigrationPathways |
P36584
|
FINISHED |
| Object | skilled migration |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: skilled migration | Statement: [Australian Iranians, immigrationPathways, skilled migration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immigrationPathways Context triple: [Australian Iranians, immigrationPathways, skilled migration]
-
A.
immigrationType
chosen
Indicates the specific category or classification of an individual’s immigration status or entry into a country.
-
B.
immigrationFeature
Indicates that an entity possesses a characteristic, policy, or attribute specifically related to immigration.
-
C.
immigrationBackground
Indicates that an entity has a personal or familial history of migration from another country or region.
-
D.
immigrationReason
Indicates the reason or motivation behind an entity’s act of immigrating from one place to another.
-
E.
immigrationPolicyFocus
Indicates a relationship where an immigration policy is primarily directed toward or emphasizes a particular issue, group, or aspect of immigration.
- F. None of above.
Provenance (3 batches)
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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c21961388190be9a7c535ed25761 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.