Triple
T14019514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Inshirah |
E337289
|
entity |
| Predicate | hasJuzPlacement |
P34330
|
FINISHED |
| Object | part of Juz 30 |
—
|
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: part of Juz 30 | Statement: [Al-Inshirah, hasJuzPlacement, part of Juz 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJuzPlacement Context triple: [Al-Inshirah, hasJuzPlacement, part of Juz 30]
-
A.
hasJuzCount
Indicates that an entity (such as a text or document) is associated with a specific number of Juz (sections or parts).
-
B.
hasJuzRange
Indicates that an entity (such as a text or passage) spans, is associated with, or falls within a specified range of Juz segments.
-
C.
quranicJuz
chosen
Indicates that a specific portion or passage belongs to, or is contained within, a particular Juz (section) of the Quran.
-
D.
hasHizbCount
Indicates the number of hizbs (sections/parts) associated with or assigned to a given entity.
-
E.
juz
Indicates a judgment or evaluation made about one entity in relation to another.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3c7cd88190b236382058581740 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.