Triple
T13451818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 21:85 |
E320624
|
entity |
| Predicate | mentionsRoleOf |
P109558
|
FINISHED |
| Object | prophets |
—
|
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: prophets | Statement: [Quran 21:85, mentionsRoleOf, prophets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsRoleOf Context triple: [Quran 21:85, mentionsRoleOf, prophets]
-
A.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
B.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
C.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
D.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
E.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaefae85481909e6a59797cbb25e7 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadce235f88190a6433395d2969811 |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:41 p.m.