Triple
T2833750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistani New Zealander |
E62300
|
entity |
| Predicate | typicalMigrationPath |
P4575
|
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: [Pakistani New Zealander, typicalMigrationPath, skilled migration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMigrationPath Context triple: [Pakistani New Zealander, typicalMigrationPath, skilled migration]
-
A.
typicalMigrationStatus
Indicates the usual or characteristic migration state or pattern associated with an entity.
-
B.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
C.
migrationPattern
chosen
Indicates the typical routes, timing, and destinations followed by entities as they move periodically from one location or region to another.
-
D.
migrationPolicy
Indicates the rules or strategies governing how entities move, transfer, or transition from one context, location, or state to another.
-
E.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec036dc8190bc2d974f6d82eda9 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.