Triple
T37991170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African peoples |
E947825
|
entity |
| Predicate | notableHistoricalEmpires |
P4200
|
FINISHED |
| Object | Mali Empire |
E67983
|
NE 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: Mali Empire | Statement: [African peoples, notableHistoricalEmpires, Mali Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHistoricalEmpires Context triple: [African peoples, notableHistoricalEmpires, Mali Empire]
-
A.
historicalEmpireCenter
Indicates that a location served as the primary political or administrative center of a historical empire.
-
B.
hasHistoricalEmpire
chosen
Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
-
C.
earliestMajorEmpire
Indicates that the subject is the earliest major empire associated with, or relevant to, the given object in time.
-
D.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
E.
eraOfHistoricalKingdom
Indicates the historical time period during which a particular kingdom existed or held prominence.
- F. None of above.
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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a412cbbe6cc81909701ceb1455ada03 |
completed | June 28, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.