Triple
T25456494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عبد المطلب بن هاشم بن عبد مناف |
E637927
|
entity |
| Predicate | الحدث_البارز |
P158542
|
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.
notableEventPromoted
Indicates that an event was actively publicized, advertised, or otherwise promoted as notable or significant.
-
B.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
C.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
D.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
E.
notableCoverEvent
Indicates that an entity has been the subject of a particularly significant or noteworthy cover version, performance, or reinterpretation by another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:09 p.m.