Triple
T28636437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abū’l-Faḍl |
E724798
|
entity |
| Predicate | sufiOrderContext |
P42510
|
FINISHED |
| Object | Shadhiliyya |
—
|
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: Shadhiliyya | Statement: [Abū’l-Faḍl, sufiOrderContext, Shadhiliyya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufiOrderContext Context triple: [Abū’l-Faḍl, sufiOrderContext, Shadhiliyya]
-
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.
hasRoleInSufism
Indicates that an entity holds a specific role, function, or position within the context of Sufism.
-
C.
establishedInOrderContext
Indicates that something was created, initiated, or set up specifically within the framework or circumstances of a particular order or ordering process.
-
D.
viewInSufism
Indicates the perspective, interpretation, or doctrinal understanding of something specifically within the context of Sufi thought or practice.
-
E.
kuficOrder
Indicates that one entity commissions, arranges, or prescribes the creation or use of Kufic script in relation to another entity.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a5dad48190ae08da40ca666cd0 |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:41 a.m.