Triple
T29808905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolof people |
E756905
|
entity |
| Predicate | famousPerson |
P80459
|
FINISHED |
| Object | Cheikh Anta Diop |
—
|
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: Cheikh Anta Diop | Statement: [Wolof people, famousPerson, Cheikh Anta Diop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousPerson Context triple: [Wolof people, famousPerson, Cheikh Anta Diop]
-
A.
famousIndividual
Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
-
B.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
-
C.
notablePublicFigure
Indicates that the subject is widely recognized and holds a significant public profile or influence in society.
-
D.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
-
E.
famousMember
chosen
Indicates that an entity is a well-known or widely recognized member of a particular group, organization, or category.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 5:22 p.m.