Triple
T14057948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sosso state |
E338266
|
entity |
| Predicate | roseToProminenceAfter |
P51037
|
FINISHED |
| Object | decline of the Ghana Empire |
—
|
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: decline of the Ghana Empire | Statement: [Sosso state, roseToProminenceAfter, decline of the Ghana Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roseToProminenceAfter Context triple: [Sosso state, roseToProminenceAfter, decline of the Ghana Empire]
-
A.
roseToProminenceUnder
Indicates that an entity became well-known, influential, or successful during the period of another entity’s leadership, guidance, or dominance.
-
B.
roseToProminenceIn
chosen
Indicates the time or context in which an entity became widely recognized, influential, or notable.
-
C.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
-
D.
wasElevatedTo
Indicates that an entity was promoted or raised to a higher rank, status, or position.
-
E.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8e6d008190af8892f34c5cefbd |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.