Triple
T9095924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wahshi ibn Harb |
E218019
|
entity |
| Predicate | laterRepentedFor |
P75734
|
FINISHED |
| Object | killing Hamza ibn Abd al-Muttalib |
—
|
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: killing Hamza ibn Abd al-Muttalib | Statement: [Wahshi ibn Harb, laterRepentedFor, killing Hamza ibn Abd al-Muttalib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRepentedFor Context triple: [Wahshi ibn Harb, laterRepentedFor, killing Hamza ibn Abd al-Muttalib]
-
A.
repentedIn
Indicates that an entity has expressed remorse or regret for its actions within a particular context, time, or situation.
-
B.
repentedTo
chosen
Indicates that one entity expressed remorse or sought forgiveness directly from another entity.
-
C.
confessedTo
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another entity.
-
D.
repudiatedAfter
Indicates that one entity formally rejects, disavows, or withdraws support for another entity after a specified time or subsequent event.
-
E.
performedPenanceAt
Indicates that an entity carried out an act of penance at a specific place or location.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b650648190a8f59cee402d12aa |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:14 p.m.