Triple
T9168257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayyub |
E220018
|
entity |
| Predicate | famousSupplicationSource |
P35890
|
FINISHED |
| Object | Quran 21:83 |
—
|
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: Quran 21:83 | Statement: [Ayyub, famousSupplicationSource, Quran 21:83]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousSupplicationSource Context triple: [Ayyub, famousSupplicationSource, Quran 21:83]
-
A.
hasTheologicalSourceIn
Indicates that something derives its theological basis, authority, or origin from a specified source.
-
B.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
C.
performedSupplication
Indicates that one entity directed a humble, earnest request or prayer (a supplication) toward another entity.
-
D.
isAddressedInPrayer
Indicates that an entity is the recipient or target of a prayer being spoken or offered.
-
E.
scriptureOrLegendSource
chosen
Indicates that something is derived from, based on, or documented in a particular scripture or legendary 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaadfb50881909b9127f92e4b3e21 |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.