Triple
T8760891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mālik Yawm ad-Dīn |
E208193
|
entity |
| Predicate | foundInChapterPosition |
P36548
|
FINISHED |
| Object | first surah of the Quran |
—
|
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: first surah of the Quran | Statement: [Mālik Yawm ad-Dīn, foundInChapterPosition, first surah of the Quran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInChapterPosition Context triple: [Mālik Yawm ad-Dīn, foundInChapterPosition, first surah of the Quran]
-
A.
foundInChapter
chosen
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
B.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
C.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
D.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
-
E.
positionInVerse
Indicates the specific ordinal location that something occupies within a verse.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5df9729481908679151988b76d2f |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.