Triple
T29584001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirifle |
E753670
|
entity |
| Predicate | associatedSufiOrders |
P42510
|
FINISHED |
| Object | Qadiriyya |
E969677
|
NE 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: Qadiriyya | Statement: [Mirifle, associatedSufiOrders, Qadiriyya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSufiOrders Context triple: [Mirifle, associatedSufiOrders, Qadiriyya]
-
A.
SufiOrder
chosen
Indicates a relationship in which an entity is affiliated with, belongs to, or is a member of a specific Sufi order.
-
B.
associatedSultan
Indicates that one entity is linked or connected to a particular sultan in some relevant context or relationship.
-
C.
associatedWithImamNumber
Indicates a relationship where an entity is linked to, or identified by, a specific numbered Imam in a sequence of Imams.
-
D.
associatedOrderFoundedIn
Indicates that an order or organization associated with an entity was founded in a specified place or time.
-
E.
ordersSurahsPrimarilyBy
Indicates that one entity arranges or sequences surahs chiefly according to a specified organizing principle or criterion.
- F. None of above.
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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a262d76941c81909e409f9551451ff4 |
completed | June 8, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 6:09 p.m.