Triple
T33208793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badawiyya Sufi order |
E850084
|
entity |
| Predicate | usesHonorificForFounder |
P96161
|
FINISHED |
| Object | wali |
—
|
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: wali | Statement: [Badawiyya Sufi order, usesHonorificForFounder, wali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHonorificForFounder Context triple: [Badawiyya Sufi order, usesHonorificForFounder, wali]
-
A.
founderHonorific
chosen
Indicates that an honorific title or respectful designation is used when referring to the founder in this relationship.
-
B.
founderHonorificTitle
Indicates that an entity holds an honorific or ceremonial title specifically in their capacity as a founder.
-
C.
honorificInitial
Indicates that one entity is the initial letter or abbreviated form of an honorific title used for another entity.
-
D.
hasHonorificNamesake
Indicates that an entity is named in honor of another entity, serving as a namesake that recognizes or commemorates the other.
-
E.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.