Triple
T15183423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة الكوثر |
E362805
|
entity |
| Predicate | تتضمن ردًا على |
P40030
|
FINISHED |
| Object | من وصف النبي بالأبتر |
—
|
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: من وصف النبي بالأبتر | Statement: [سورة الكوثر, تتضمن ردًا على, من وصف النبي بالأبتر]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: تتضمن ردًا على Context triple: [سورة الكوثر, تتضمن ردًا على, من وصف النبي بالأبتر]
-
A.
includesResponse
chosen
Indicates that one entity contains, incorporates, or encompasses another entity as a response or reply.
-
B.
responseScope
Indicates the extent, boundaries, or range of content, issues, or elements that a given response is intended to address.
-
C.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
D.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
-
E.
responseField
Indicates that a particular piece of information is included as part of a response or output structure.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006663ad48190986b680001be0e9b |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.