Triple
T7994230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bantu peoples |
E186082
|
entity |
| Predicate | migrationBeganApprox |
P80235
|
FINISHED |
| Object | 3000 BCE |
—
|
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: 3000 BCE | Statement: [Bantu peoples, migrationBeganApprox, 3000 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migrationBeganApprox Context triple: [Bantu peoples, migrationBeganApprox, 3000 BCE]
-
A.
migrationBackground
Indicates that an entity has a personal or familial history of moving from one country or region to another, typically across national borders.
-
B.
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.
-
C.
migrationEnded
Indicates that a previously ongoing migration process or movement from one place or state to another has come to an end.
-
D.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
E.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
- F. None of above. chosen
Provenance (4 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c73ba388190bcedc29fbdd22f3c |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:16 p.m.