Triple
T26757323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 18:1–110 |
E674708
|
entity |
| Predicate | hasBasmala |
P35246
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Quran 18:1–110, hasBasmala, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasmala Context triple: [Quran 18:1–110, hasBasmala, Yes]
-
A.
containsBasmalah
chosen
Indicates that something (such as a text, document, or verse) includes the Basmalah phrase ("In the name of God, the Most Gracious, the Most Merciful") within it.
-
B.
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.
-
C.
hasOpeningWordsArabic
Indicates that an entity (such as a text, document, or work) has specific opening words expressed in the Arabic language.
-
D.
containsMakkiVerses
Indicates that something (typically a chapter or section of a text) includes one or more verses that are classified as Makki (revealed in Mecca).
-
E.
hasLatinIncipit
Indicates that an entity begins with, or is identified by, a specified Latin opening phrase (incipit).
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 3:56 a.m.