Triple
T14436737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة الهمزة |
E357981
|
entity |
| Predicate | تتضمن أسلوباً |
P10363
|
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.
includesApproach
chosen
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity or context.
-
B.
approachStyle
Indicates the manner or strategy with which one entity moves toward, engages with, or initiates interaction with another entity or target.
-
C.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
-
D.
partOfStyle
Indicates that one style is a component, subset, or constituent element of another, more encompassing style.
-
E.
broughtStyleTo
Indicates that one entity introduced or contributed a particular style or aesthetic to another entity or context.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9148cf4481909082cc91b2f76218 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.