Triple
T12209093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraqi diaspora |
E290908
|
entity |
| Predicate | hasMigrationCause |
P42539
|
FINISHED |
| Object | political persecution |
—
|
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: political persecution | Statement: [Iraqi diaspora, hasMigrationCause, political persecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMigrationCause Context triple: [Iraqi diaspora, hasMigrationCause, political persecution]
-
A.
hasMigrationIssue
Indicates that an entity experiences a problem, error, or complication during a migration process from one system, environment, or version to another.
-
B.
hasMigrationHistoryFrom
Indicates that an entity has a recorded history of migrating or moving from a specified origin location or source.
-
C.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
D.
hasMigrationAspect
Indicates that something possesses a characteristic, feature, or dimension specifically related to migration or migratory behavior.
-
E.
migrationCause
chosen
Indicates the reason or driving factor that leads an entity to migrate 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.