Triple
T212790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seal of the Prophets |
E4753
|
entity |
| Predicate | mentionedInVerse |
P5301
|
FINISHED |
| Object | Qur’an 33:40 |
—
|
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: Qur’an 33:40 | Statement: [Seal of the Prophets, mentionedInVerse, Qur’an 33:40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInVerse Context triple: [Seal of the Prophets, mentionedInVerse, Qur’an 33:40]
-
A.
mentions
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
B.
scriptureAllusion
Indicates that one entity makes reference to, echoes, or is inspired by a passage, theme, or element from a scriptural text found in another entity.
-
C.
scripturalAllusion
Indicates that one entity references, echoes, or draws upon content, themes, or language from a scriptural or sacred text in relation to another entity.
-
D.
scripturalReference
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
-
E.
notedIn
chosen
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c313d108190a65d3e939f961bef |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.