Triple
T25456501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عبد المطلب بن هاشم بن عبد مناف |
E637927
|
entity |
| Predicate | سبب_اللقب |
P9593
|
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.
reasonForEpithet
chosen
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
B.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
C.
reasonForNickname
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
D.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
E.
سبب التسمية
Indicates the reason or cause behind assigning a particular name to something.
- 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_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:10 p.m.