Triple
T12374698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Mursalat |
E295091
|
entity |
| Predicate | oathsAbout |
P104641
|
FINISHED |
| Object | winds sent forth |
—
|
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: winds sent forth | Statement: [Al-Mursalat, oathsAbout, winds sent forth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oathsAbout Context triple: [Al-Mursalat, oathsAbout, winds sent forth]
-
A.
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.
-
B.
religionInOath
Indicates that a religious element, such as a deity, scripture, or religious principle, is invoked or referenced within an oath or sworn statement.
-
C.
oathTextDefinedIn
Indicates that the specific wording or content of an oath is defined or specified within a particular document, source, or context.
-
D.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific entity.
-
E.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fa8ca7c8190b3f8e9c2ec23e837 |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93fa244148190a960be3ff6f1cf45 |
completed | April 10, 2026, 6:21 p.m. |
Created at: April 8, 2026, 9:54 p.m.