Triple
T22022955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diop |
E543886
|
entity |
| Predicate | isPatronymicIn |
P146304
|
FINISHED |
| Object | Wolof naming traditions |
—
|
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: Wolof naming traditions | Statement: [Diop, isPatronymicIn, Wolof naming traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPatronymicIn Context triple: [Diop, isPatronymicIn, Wolof naming traditions]
-
A.
isPatronymicName
Indicates that a name is derived from a father’s or ancestor’s given name, typically signifying lineage or descent.
-
B.
isPatronymicSurname
Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
-
C.
isPatronymicOrToponymic
Indicates that a name or term is derived either from a person's name (patronymic) or from a place name (toponymic).
-
D.
hasPatronymicUse
Indicates that an entity uses a patronymic form of naming derived from a parent’s (typically the father’s) given name.
-
E.
hasPatronymicDerivative
Indicates that one name or term is derived from another by forming a patronymic, typically expressing descent or lineage from a person.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c9959481908da6bed356199f75 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:23 p.m.