Triple
T1822363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah As-Saffat |
E40568
|
entity |
| Predicate | containsOathBy |
P31562
|
FINISHED |
| Object | those who set the ranks |
—
|
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: those who set the ranks | Statement: [Surah As-Saffat, containsOathBy, those who set the ranks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsOathBy Context triple: [Surah As-Saffat, containsOathBy, those who set the ranks]
-
A.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
B.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
C.
oathSwornBefore
Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
-
D.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific entity.
-
E.
hasSwornStatus
Indicates that an entity is formally bound by an oath or sworn commitment, reflecting an official or pledged status in relation to another entity or role.
- 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_69a8864526c081908a3a4d74f689e2c5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab21ab83a48190a33afe5db19a21f8 |
completed | March 6, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61d97d008190b6642aef32eb7e36 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab21aa56108190a5123539d5020741 |
completed | March 6, 2026, 6:49 p.m. |
Created at: March 4, 2026, 7:32 p.m.