Triple
T7254023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghawth al-Azam |
E157672
|
entity |
| Predicate | linkedToOrderSpread |
P2899
|
FINISHED |
| Object | global expansion of the Qadiriyya order |
—
|
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: global expansion of the Qadiriyya order | Statement: [Ghawth al-Azam, linkedToOrderSpread, global expansion of the Qadiriyya order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToOrderSpread Context triple: [Ghawth al-Azam, linkedToOrderSpread, global expansion of the Qadiriyya order]
-
A.
spreadsAs
Indicates that one entity propagates, extends, or disseminates from another entity or source.
-
B.
refersToOrder
Indicates that one entity makes reference to, or is associated with, a specific order.
-
C.
sponsoringOrder
Indicates that one entity provides sponsorship or financial backing for another entity’s order or purchase.
-
D.
spreadBy
chosen
Indicates that something is transmitted, dispersed, or propagated through the agency or action of a specified entity or medium.
-
E.
hasExchangeRateSpreadWith
Indicates a relationship where the difference (spread) between two entities’ exchange rates is defined or measured.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9f55b4819081a43e7a01eda154 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.