Triple
T25456536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | شيبة الحمد |
E637928
|
entity |
| Predicate | الحدث المشهور |
P103404
|
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 that something serves as the reason or basis for another thing’s historical significance.
-
B.
محاكمة
Indicates that a legal trial or judicial proceeding is being conducted involving the entities.
-
C.
السمعة
chosen
Indicates the reputation or public perception associated with an entity based on others’ opinions or past actions.
-
D.
סיבת זכייה
Indicates the reason or cause for which an entity wins or is awarded something.
-
E.
التأثير
Indicates a relationship where one entity produces a change or has an influence on another entity or its state.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72756748190aa315cc00882a798 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:10 p.m.