Triple
T25347331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Ghunya li-Talibi Tariq al-Haqq |
E635586
|
entity |
| Predicate | associatedWithSufism |
P42510
|
FINISHED |
| Object | Qadiriyya order |
—
|
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: Qadiriyya order | Statement: [Al-Ghunya li-Talibi Tariq al-Haqq, associatedWithSufism, Qadiriyya order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSufism Context triple: [Al-Ghunya li-Talibi Tariq al-Haqq, associatedWithSufism, Qadiriyya order]
-
A.
hasRoleInSufism
Indicates that an entity holds a specific role, function, or position within the context of Sufism.
-
B.
viewOnSufism
Indicates a person's stance, opinion, or perspective regarding Sufism.
-
C.
SufiOrder
chosen
Indicates a relationship in which an entity is affiliated with, belongs to, or is a member of a specific Sufi order.
-
D.
viewInSufism
Indicates the perspective, interpretation, or doctrinal understanding of something specifically within the context of Sufi thought or practice.
-
E.
associatedWithMosque
Indicates a relationship where an entity has a connection or affiliation with a mosque, such as through location, use, administration, or religious function.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 21, 2026, 1:34 p.m.