Triple
T34316703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abd Allah ibn Hanzala |
E880603
|
entity |
| Predicate | consequenceOfRevolt |
P9821
|
FINISHED |
| Object | Umayyad army sent against Medina |
—
|
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: Umayyad army sent against Medina | Statement: [Abd Allah ibn Hanzala, consequenceOfRevolt, Umayyad army sent against Medina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfRevolt Context triple: [Abd Allah ibn Hanzala, consequenceOfRevolt, Umayyad army sent against Medina]
-
A.
resultOfUprising
chosen
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
B.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
C.
endCauseOfRevolt
Indicates that the subject is the cause or factor that brings a revolt or uprising to an end.
-
D.
actsOfRebellion
Indicates actions that deliberately oppose, resist, or defy an established authority, rule, or controlling force.
-
E.
endOfRebellion
Indicates that a rebellion or uprising has concluded or been brought to an end.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 1, 2026, 1:57 a.m.