Triple
T3508432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Al-Kawthar |
E74137
|
entity |
| Predicate | kuficOrder |
P48414
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Surah Al-Kawthar, kuficOrder, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kuficOrder Context triple: [Surah Al-Kawthar, kuficOrder, 15]
-
A.
hasStrokeOrder
Indicates that there is a specific, ordered sequence of strokes used to write or draw the related symbol or character.
-
B.
SufiOrder
Indicates a relationship in which an entity is affiliated with, belongs to, or is a member of a specific Sufi order.
-
C.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
D.
positionInKutubAlSittah
Indicates the specific placement or ordering of a text or hadith within the canonical six-book collection of Sunni hadith, known as Kutub al-Sittah.
-
E.
containsMuqattaat
Indicates that the referenced text or verse includes muqattaat, the disjointed or abbreviated Arabic letters that appear at the beginnings of some Quranic chapters.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc0cc394819087a9b598023f4f93 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:18 p.m.