Triple
T15350953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة تبت |
E367048
|
entity |
| Predicate | تتضمن معنى |
P102770
|
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.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
meaningInContext
chosen
Indicates that one entity represents or conveys a particular meaning, interpretation, or sense within a specific context or situation.
-
C.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
D.
sharesMeaningWith
Indicates that two expressions convey the same or very similar meaning, even if they differ in form or wording.
-
E.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e290efc8190b22c95dcd3e5f57f |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.