Triple
T25843607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة الأعراف |
E651002
|
entity |
| Predicate | اسمها مشتق من |
P64332
|
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.
familyNameDerivedFrom
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
B.
dynasticNameDerivedFrom
Indicates that a dynastic name is derived from, or based on, another name, title, or source.
-
C.
nameEtymologyFor
chosen
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
D.
brandNameDerivedFrom
Indicates that the brand’s name is derived from, based on, or taken from another specified name or source.
-
E.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6023662a48190b8eb77eebc225c36 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:51 a.m.