Triple
T9559885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ad-Dukhan |
E230640
|
entity |
| Predicate | consideredSacredTextBy |
P60571
|
FINISHED |
| Object | Muslims |
—
|
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: Muslims | Statement: [Ad-Dukhan, consideredSacredTextBy, Muslims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredSacredTextBy Context triple: [Ad-Dukhan, consideredSacredTextBy, Muslims]
-
A.
regardedAsScriptureBy
Indicates that something is considered to be sacred scripture or canonical religious text by a particular person, group, or tradition.
-
B.
hasSacredText
Indicates that an entity possesses or is associated with a particular sacred or religious text.
-
C.
consideredScriptureBy
chosen
Indicates that one party regards or recognizes a text or writing as sacred scripture.
-
D.
isAssociatedWithReligiousText
Indicates a relationship where an entity is connected or linked in some way to a religious text, such as being based on, derived from, or directly related to it.
-
E.
usedForReligiousTexts
Indicates that something is used in the creation, preservation, or practice of religious texts or scriptures.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994bde0c8190afcba5cb8fa8b984 |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.