Triple
T19970534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | וַשְׁתִּי |
E480058
|
entity |
| Predicate | hasQuranicStatus |
P17714
|
FINISHED |
| Object | not mentioned in the Quran |
—
|
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: not mentioned in the Quran | Statement: [וַשְׁתִּי, hasQuranicStatus, not mentioned in the Quran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuranicStatus Context triple: [וַשְׁתִּי, hasQuranicStatus, not mentioned in the Quran]
-
A.
quranicStatus
chosen
Indicates the status or classification of something in relation to its recognition, treatment, or role within the Quran.
-
B.
hasQuranicDescription
Indicates that there exists a description or characterization of the subject that is explicitly given or referenced in the Quran.
-
C.
statusInHadith
Indicates the classification or standing of a hadith (such as authentic, weak, or fabricated) within hadith scholarship.
-
D.
hasQuranicEquivalent
Indicates that something has a corresponding or analogous concept, term, or passage found in the Quran.
-
E.
hasQuranicVerseReference
Indicates that an entity is associated with, or refers to, a specific verse or verses from the Quran.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc89b508190879d29bef546aac8 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.