Triple
T32610083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese Canadians |
E833629
|
entity |
| Predicate | linkedToMigrationCause |
P42539
|
FINISHED |
| Object | economic 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: economic migration | Statement: [Portuguese Canadians, linkedToMigrationCause, economic migration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToMigrationCause Context triple: [Portuguese Canadians, linkedToMigrationCause, economic migration]
-
A.
migrationCause
chosen
Indicates the reason or driving factor that leads an entity to migrate from one place to another.
-
B.
associatedWithMigration
Indicates a relationship or connection between entities that is linked to, results from, or occurs in the context of migration.
-
C.
associatedWithMigrationType
Indicates that one entity has a specified connection or linkage to a particular type or category of migration.
-
D.
linkedToCause
Indicates that one entity is connected or related to another as a contributing factor or cause of it.
-
E.
hasReasonForMigration
Indicates that there exists a specific cause, motive, or justification for an entity’s act of migrating from one place to another.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 1, 2026, 1:06 a.m.