Triple
T13826804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hind bint Abi Umayya |
E332270
|
entity |
| Predicate | marriedProphetMuhammadAfter |
P111662
|
FINISHED |
| Object | death of Abu Salama |
—
|
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: death of Abu Salama | Statement: [Hind bint Abi Umayya, marriedProphetMuhammadAfter, death of Abu Salama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedProphetMuhammadAfter Context triple: [Hind bint Abi Umayya, marriedProphetMuhammadAfter, death of Abu Salama]
-
A.
wasMarriedBeforeProphet
Indicates that a person had been married at least once prior to the time of becoming a prophet.
-
B.
marriageToProphetOccurredIn
Indicates that the marriage to the prophet took place in a specified location or context.
-
C.
marriageToMuhammadType
Indicates a marital relationship in which the person is (or was) married to Muhammad, specifying that the marriage is to the individual identified as Muhammad.
-
D.
yearOfMarriageToMuhammad_CommonEra
Indicates the calendar year in the Common Era when an individual married Muhammad.
-
E.
yearOfMarriageToMuhammad_Hijri
Indicates the Hijri calendar year in which an individual married the Prophet Muhammad.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0295d2d48190b08eba0d805bd72d |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:13 p.m.