Triple
T31335767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic East |
E799168
|
entity |
| Predicate | hasSufiOrder |
P1109
|
FINISHED |
| Object | Naqshbandi 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: Naqshbandi order | Statement: [Islamic East, hasSufiOrder, Naqshbandi order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSufiOrder Context triple: [Islamic East, hasSufiOrder, Naqshbandi order]
-
A.
hasOrder
chosen
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
hasSVOOrder
Indicates that a language or construction follows a basic word order where the subject comes first, followed by the verb, and then the object.
-
C.
isOrderOf
Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
-
D.
isOrderIn
Indicates that one entity is contained within or belongs to a specified order or sequence of entities.
-
E.
hasTraditionalOrderFollowedBy
Indicates that one item directly succeeds another according to an established or customary ordering.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: April 29, 2026, 9:16 p.m.