Triple
T9508490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ornaments of Gold |
E229330
|
entity |
| Predicate | hasQuranicOrder |
P49155
|
FINISHED |
| Object | 43 |
—
|
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: 43 | Statement: [The Ornaments of Gold, hasQuranicOrder, 43]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuranicOrder Context triple: [The Ornaments of Gold, hasQuranicOrder, 43]
-
A.
hasVerseOrder
Indicates that one verse is ordered or sequenced in relation to another verse within a structured text.
-
B.
quranicStatus
Indicates the status or classification of something in relation to its recognition, treatment, or role within the Quran.
-
C.
revealedInArabicOrder
chosen
Indicates that something was disclosed or made known following the original sequence in which it was revealed in Arabic.
-
D.
kuficOrder
Indicates that one entity commissions, arranges, or prescribes the creation or use of Kufic script in relation to another entity.
-
E.
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.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9855c5e48190a7d8d39b6d601679 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.