Triple
T4303884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saho people |
E99905
|
entity |
| Predicate | ritualSpecialists |
P17182
|
FINISHED |
| Object | Islamic scholars (ulama) |
—
|
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: Islamic scholars (ulama) | Statement: [Saho people, ritualSpecialists, Islamic scholars (ulama)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualSpecialists Context triple: [Saho people, ritualSpecialists, Islamic scholars (ulama)]
-
A.
ritualSpecialist
chosen
Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
-
B.
ritualCharacteristics
Indicates the defining features, practices, or attributes that characterize a particular ritual.
-
C.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
D.
ritualPurpose
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
-
E.
hasRitualFocus
Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350b792608190ac778b79c740256a |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b347ff45cc8190b0cc335a94cc3d73 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:09 p.m.