Triple
T12804468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Inshiqaq |
E306107
|
entity |
| Predicate | hasFirstVerse |
P36750
|
FINISHED |
| Object | إِذَا السَّمَاءُ انشَقَّتْ |
—
|
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: إِذَا السَّمَاءُ انشَقَّتْ | Statement: [Al-Inshiqaq, hasFirstVerse, إِذَا السَّمَاءُ انشَقَّتْ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstVerse Context triple: [Al-Inshiqaq, hasFirstVerse, إِذَا السَّمَاءُ انشَقَّتْ]
-
A.
hasVerseCount
Indicates that an entity (such as a text or section) is associated with a specific number of verses it contains.
-
B.
hasVerseOrder
Indicates that one verse is ordered or sequenced in relation to another verse within a structured text.
-
C.
firstVerseText
chosen
Indicates the textual content that appears in the first verse of something, such as a song, poem, or hymn.
-
D.
hasVersesIn
Indicates that one entity (typically a text, chapter, or section) contains or is composed of verses found within another entity (such as a book, collection, or scripture).
-
E.
hasVerseRange
Indicates a relationship where a text or passage is associated with a specific contiguous range of verses it spans.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7e3be48190ba9159c9f1ac2ccd |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.