Triple
T30519151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikelan |
E776644
|
entity |
| Predicate | contemporaryChange |
P178822
|
FINISHED |
| Object | legal abolition of slavery in Sahel states |
—
|
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: legal abolition of slavery in Sahel states | Statement: [Ikelan, contemporaryChange, legal abolition of slavery in Sahel states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryChange Context triple: [Ikelan, contemporaryChange, legal abolition of slavery in Sahel states]
-
A.
contemporary
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
B.
contemporaryTendency
Indicates that one entity reflects, aligns with, or exemplifies a prevailing trend, style, or tendency of the same time period as another entity.
-
C.
contemporaryState
Indicates that two entities exist or occur during the same time period or historical era.
-
D.
contemporaryEvents
Indicates that two or more events occur in the same time period or overlap temporally.
-
E.
contemporaryProcess
Indicates that one process occurs in the same time period as, or overlaps temporally with, another process.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 29, 2026, 8:17 p.m.