Triple
T9993120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian diaspora |
E196936
|
entity |
| Predicate | hasMigrationType |
P9105
|
FINISHED |
| Object | overseas 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: overseas migration | Statement: [Italian diaspora, hasMigrationType, overseas migration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMigrationType Context triple: [Italian diaspora, hasMigrationType, overseas migration]
-
A.
hasMigrationDriver
Indicates that one factor or condition serves as a driving cause or motivation for a migration event or process.
-
B.
associatedWithMigrationType
chosen
Indicates that one entity has a specified connection or linkage to a particular type or category of migration.
-
C.
hasMigrationHistoryFrom
Indicates that an entity has a recorded history of migrating or moving from a specified origin location or source.
-
D.
hasMigrationIssue
Indicates that an entity experiences a problem, error, or complication during a migration process from one system, environment, or version to another.
-
E.
hasTransformationType
Indicates that an entity undergoes or is associated with a specific kind or category of transformation.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcb96c7308190902802ef5df764c1 |
completed | April 2, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.