Triple
T26309305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | المدمدمة |
E661775
|
entity |
| Predicate | مصدر_التسمية |
P36337
|
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.
labelOf
Indicates that one entity serves as the name, tag, or identifying label assigned to another entity.
-
B.
namingBasis
Indicates that one entity serves as the reason, source, or criterion for how another entity is named or designated.
-
C.
usedAsNameSourceFor
chosen
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
-
D.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
E.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee64ce08190b9fbede178cc6f28 |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:21 p.m.