Triple
T3268165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Al-Alaq |
E68577
|
entity |
| Predicate | firstRevealedVerses |
P46989
|
FINISHED |
| Object | verses 1–5 |
—
|
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: verses 1–5 | Statement: [Surah Al-Alaq, firstRevealedVerses, verses 1–5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRevealedVerses Context triple: [Surah Al-Alaq, firstRevealedVerses, verses 1–5]
-
A.
revelationScripture
Indicates that a scripture is the medium or content through which a revelation is communicated or expressed.
-
B.
firstRevelationNear
Indicates that an entity’s initial revelation, disclosure, or divine communication occurred in the vicinity of a specified place or reference entity.
-
C.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
D.
firstRevelationPlace
Indicates the location where something (typically a text, message, or revelation) was first revealed or disclosed.
-
E.
timeOfFirstRevelation
Indicates the specific time at which the first revelation or initial disclosure of something occurred.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafcf9c6c819092f9c618b778b46d |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.