Triple
T38434017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banu Hanifa |
E903884
|
entity |
| Predicate | laterRebelled |
P184101
|
FINISHED |
| Object | after the death of Prophet Muhammad |
—
|
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: after the death of Prophet Muhammad | Statement: [Banu Hanifa, laterRebelled, after the death of Prophet Muhammad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRebelled Context triple: [Banu Hanifa, laterRebelled, after the death of Prophet Muhammad]
-
A.
holderRebelledAgainst
chosen
Indicates that the holder engaged in rebellion or uprising against the referenced entity.
-
B.
actsOfRebellion
Indicates actions that deliberately oppose, resist, or defy an established authority, rule, or controlling force.
-
C.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
D.
rebelsAgainst
Indicates that one entity actively resists, opposes, or rises up against the authority, control, or established order represented by another entity.
-
E.
statusAfterRebellion
Indicates the condition or standing of an entity after participating in or experiencing a rebellion.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0174142430819084aa1235500b9d3b |
completed | May 11, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_6a0171a6e0088190958679bb6cb24a70 |
completed | May 11, 2026, 6:05 a.m. |
Created at: May 3, 2026, 4:31 p.m.