Triple
T28238829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamna bint Jahsh |
E711960
|
entity |
| Predicate | husbandKilledAtUhud |
P164145
|
FINISHED |
| Object | Musab ibn Umayr |
—
|
NE NERFINISHED |
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: Musab ibn Umayr | Statement: [Hamna bint Jahsh, husbandKilledAtUhud, Musab ibn Umayr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: husbandKilledAtUhud Context triple: [Hamna bint Jahsh, husbandKilledAtUhud, Musab ibn Umayr]
-
A.
roleAtBattleOfUhud
Indicates the specific role, position, or function an entity held or performed during the Battle of Uhud.
-
B.
numberOfHusbandsKilled
Indicates the count of husbands that an entity has killed.
-
C.
causeOfHusbandDeath
Indicates that the subject is the cause or reason for the husband’s death.
-
D.
newsOfHusbandsDeathBroughtBy
Indicates that the news of a husband's death is delivered or communicated by a particular person or source.
-
E.
spouseExecuted
Indicates that one person’s spouse was put to death, typically as a result of a legal or extrajudicial execution.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c3aab88190842770d1bc058c07 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:56 p.m.