Triple
T25542811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zulaykha |
E640215
|
entity |
| Predicate | hasSpiritualReadingBy |
P167049
|
FINISHED |
| Object | Sufi authors |
—
|
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: Sufi authors | Statement: [Zulaykha, hasSpiritualReadingBy, Sufi authors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpiritualReadingBy Context triple: [Zulaykha, hasSpiritualReadingBy, Sufi authors]
-
A.
auraReading
Indicates perceiving and interpreting another entity’s subtle energy field or aura.
-
B.
hasSpiritualInterestIn
Indicates a relationship where one entity is spiritually drawn to, concerned with, or engaged in the religious or metaphysical aspects of another entity.
-
C.
hasSpiritualHead
Indicates that one entity serves as the primary religious or spiritual leader or authority for another entity.
-
D.
recognizesSpirit
Indicates that one entity acknowledges, identifies, or affirms the spiritual nature, presence, or authority of another entity.
-
E.
hasSpiritualSource
Indicates that something originates from, is derived from, or is fundamentally grounded in a spiritual or non-material source.
- F. None of above. chosen
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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 21, 2026, 3:26 p.m.