Triple
T14550208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Clot |
E341394
|
entity |
| Predicate | hasCanonicalOrderInQuran |
P114903
|
FINISHED |
| Object | 96 |
—
|
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: 96 | Statement: [The Clot, hasCanonicalOrderInQuran, 96]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalOrderInQuran Context triple: [The Clot, hasCanonicalOrderInQuran, 96]
-
A.
hasQuranicVerseReference
Indicates that an entity is associated with, or refers to, a specific verse or verses from the Quran.
-
B.
isMeccanSurah
Indicates that a given surah (chapter of the Qur’an) was revealed in Mecca (i.e., is classified as a Meccan surah) rather than in Medina.
-
C.
hasVerseOrder
Indicates that one verse is ordered or sequenced in relation to another verse within a structured text.
-
D.
quranManzil
Indicates a relationship where a portion of the Quran is assigned or associated as a specific “manzil” (section) for recitation or division purposes.
-
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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ed2b4c8190945bd26531c71f1f |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:23 a.m.