Triple
T32838566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | محمد فوزي |
E839900
|
entity |
| Predicate | عانى_من |
P91920
|
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.
sufferedCondition
chosen
Indicates that an entity experienced or was afflicted by a particular condition, typically adverse or harmful, at some point in time.
-
B.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
C.
sufferedDamageTo
Indicates that one entity has experienced harm, loss, or deterioration affecting another entity or one of its parts.
-
D.
hadCondition
Indicates that an entity experienced or was diagnosed with a particular medical or health-related condition.
-
E.
actedDespiteWounds
Indicates that an entity performed an action or fulfilled a role even though it was wounded or injured at the time.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:16 a.m.