Triple
T36427468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة الحجرات |
E897340
|
entity |
| Predicate | تتضمن آية |
P24842
|
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.
includesSaying
chosen
Indicates that one entity (such as a text, speech, or communication) contains or incorporates a particular saying, phrase, or quoted expression.
-
B.
lineIncludes
Indicates that a specific line (such as a text line, code line, or route segment) contains or encompasses a given element or component.
-
C.
issueIncludes
Indicates that an issue or problem encompasses, contains, or involves a specified element, component, or sub-issue as part of its scope.
-
D.
أول آية
Indicates that something is the first verse of a text, typically within a chapter or surah.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.