Triple
T22526187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | صفوت الشريف |
E556909
|
entity |
| Predicate | صلة |
P148722
|
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.
ייחוס
Indicates an attribution or assignment relationship, where a property, role, or characteristic is ascribed from one entity to another.
-
B.
ties
Indicates that one entity fastens, secures, or binds another entity (or two entities together), typically using a flexible connector such as a string, rope, or similar medium.
-
C.
التأثير
Indicates a relationship where one entity produces a change or has an influence on another entity or its state.
-
D.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
E.
سبب التسمية
Indicates the reason or cause behind assigning a particular name to something.
- F. None of above. chosen
Provenance (4 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed352b48190a96ef2896f2978cd |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:51 p.m.