Triple
T27433503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatib ibn Abi Baltaah |
E690712
|
entity |
| Predicate | reasonForPardon |
P133554
|
FINISHED |
| Object | participation in the Battle of Badr |
—
|
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: participation in the Battle of Badr | Statement: [Hatib ibn Abi Baltaah, reasonForPardon, participation in the Battle of Badr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForPardon Context triple: [Hatib ibn Abi Baltaah, reasonForPardon, participation in the Battle of Badr]
-
A.
pardonReason
chosen
Indicates the reason or justification for which a pardon is granted.
-
B.
pardonOrClemencyBy
Indicates that an authority grants a pardon or clemency to someone, forgiving or reducing their legal penalties.
-
C.
typeOfClemency
Indicates the specific kind or category of clemency granted in a clemency-related action or decision.
-
D.
soughtPardonFor
Indicates that one entity requested or attempted to obtain a formal pardon or forgiveness for another entity or for a specific action.
-
E.
posthumousPardonGrantedBy
Indicates that a formal pardon was granted to an individual after their death by a specified authority or institution.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 12:43 p.m.