Triple
T496623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian New Zealander |
E10306
|
entity |
| Predicate | migrationType |
P9105
|
FINISHED |
| Object | immigrant community |
—
|
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: immigrant community | Statement: [Asian New Zealander, migrationType, immigrant community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migrationType Context triple: [Asian New Zealander, migrationType, immigrant community]
-
A.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
-
B.
migrationPattern
Indicates the typical routes, timing, and destinations followed by entities as they move periodically from one location or region to another.
-
C.
migrationEvent
Indicates an event in which one or more entities move or relocate from one place or context to another, typically across defined boundaries or regions.
-
D.
associatedWithMigrationType
chosen
Indicates that one entity has a specified connection or linkage to a particular type or category of migration.
-
E.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f116f1b4819082f88d6c747368ae |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.