Triple
T30214053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ʿAbd al-Raḥmān ibn Muʿāwiya |
E768148
|
entity |
| Predicate | migratedVia |
P62945
|
FINISHED |
| Object | North Africa |
—
|
NE NERFINISHED |
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: North Africa | Statement: [ʿAbd al-Raḥmān ibn Muʿāwiya, migratedVia, North Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migratedVia Context triple: [ʿAbd al-Raḥmān ibn Muʿāwiya, migratedVia, North Africa]
-
A.
migratedAcross
chosen
Indicates movement of an entity from one side of a boundary, region, or area to the other, typically implying a significant relocation or crossing.
-
B.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
C.
establishedAfterMigrationFrom
Indicates that one entity was established only after another entity had migrated from a previous location or context.
-
D.
migrationCause
Indicates the reason or driving factor that leads an entity to migrate from one place to another.
-
E.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff359688190bb36d178d11fdb04 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:33 p.m.