Triple
T29449568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogon traditional religion |
E746938
|
entity |
| Predicate | hogonRole |
P167201
|
FINISHED |
| Object | spiritual leader |
—
|
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: spiritual leader | Statement: [Dogon traditional religion, hogonRole, spiritual leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hogonRole Context triple: [Dogon traditional religion, hogonRole, spiritual leader]
-
A.
HodRole
Indicates that an entity holds the role or position of Head of Department (HOD) in relation to a specified department or organizational unit.
-
B.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
C.
gammaRole
Indicates a tertiary or supporting role that an entity plays within a structured hierarchy of roles or participants in an event or relationship.
-
D.
honorsRoleAs
Indicates that one entity shows respect, recognition, or deference to another entity specifically in their official position or function.
-
E.
eraRole
Indicates the specific role, function, or capacity an entity has within a particular historical or temporal era.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b661648819084ef0f2cee9dbe45 |
completed | May 2, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3:31 p.m.