Triple
T15577687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة لهب |
E374409
|
entity |
| Predicate | مخاطَبها |
P40250
|
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.
correspondedWith
Indicates that two entities engaged in mutual communication, typically by exchanging messages or letters over a period of time.
-
B.
التأثير
Indicates a relationship where one entity produces a change or has an influence on another entity or its state.
-
C.
intendedMessage
Indicates that one entity is the message or content that another entity aims or plans to communicate.
-
D.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
E.
communicatesTo
chosen
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e22c89081909b1ec0cd36a1ef45 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.