Triple
T7912495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhul-Qarnayn |
E183732
|
entity |
| Predicate | mentionedInSurahNumber |
P71343
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [Dhul-Qarnayn, mentionedInSurahNumber, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInSurahNumber Context triple: [Dhul-Qarnayn, mentionedInSurahNumber, 18]
-
A.
occursInSurah
chosen
Indicates that something (such as a verse, concept, or event) takes place within or is contained in a specific surah.
-
B.
quranicSurahMention
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
-
C.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
D.
quranSurahNumber
Indicates the numerical position or identifier assigned to a specific surah (chapter) within the Quran.
-
E.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a7383cc819084eab19799209d2e |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:04 p.m.