Triple
T9065540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheikh Adi ibn Musafir |
E217234
|
entity |
| Predicate | coreStatusInYazidism |
P86760
|
FINISHED |
| Object | central saint |
—
|
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: central saint | Statement: [Sheikh Adi ibn Musafir, coreStatusInYazidism, central saint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreStatusInYazidism Context triple: [Sheikh Adi ibn Musafir, coreStatusInYazidism, central saint]
-
A.
statusInIslamicTradition
Indicates the recognized standing, role, or level of esteem an entity holds within Islamic religious, cultural, or scholarly tradition.
-
B.
statusInHadith
Indicates the classification or standing of a hadith (such as authentic, weak, or fabricated) within hadith scholarship.
-
C.
politicalStatusPreIslam
Indicates the political condition, role, or organization that existed before the advent or establishment of Islam.
-
D.
caliphalLineStatus
Indicates the status or condition of a particular caliphal line within a broader succession or dynastic context.
-
E.
quranicStatus
Indicates the status or classification of something in relation to its recognition, treatment, or role within the Quran.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc94bc91d48190acf62afa90eec079 |
completed | April 1, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:11 p.m.