Triple
T37991522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akan diaspora |
E947830
|
entity |
| Predicate | maintainsHistoricalMemoryOf |
P145824
|
FINISHED |
| Object | Asante Empire |
—
|
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: Asante Empire | Statement: [Akan diaspora, maintainsHistoricalMemoryOf, Asante Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsHistoricalMemoryOf Context triple: [Akan diaspora, maintainsHistoricalMemoryOf, Asante Empire]
-
A.
retainsMemoriesOf
chosen
Indicates that one entity continues to hold or preserve memories about another entity or about events involving that entity.
-
B.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
C.
rememberedThrough
Indicates that one entity is remembered, commemorated, or kept in memory by means of, or through the influence of, another entity or medium.
-
D.
historicallyKeptAt
Indicates that an entity was stored or maintained at a particular location during a past period of time.
-
E.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:20 p.m.