Triple
T33846992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teso–Turkana group |
E867507
|
entity |
| Predicate | historicalMigrationRegion |
P19590
|
FINISHED |
| Object | Karamoja cluster region |
—
|
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: Karamoja cluster region | Statement: [Teso–Turkana group, historicalMigrationRegion, Karamoja cluster region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMigrationRegion Context triple: [Teso–Turkana group, historicalMigrationRegion, Karamoja cluster region]
-
A.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
B.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
C.
historicalPopulationMovement
chosen
Indicates the movement or migration of a population from one place to another during a specific historical period or event.
-
D.
historicalStatusOfRegion
Indicates the historical political or administrative status that a region held during a specific past period.
-
E.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:47 a.m.