Triple
T16005109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bussa |
E388196
|
entity |
| Predicate | revoltOutcome |
P94217
|
FINISHED |
| Object | revolt suppressed by colonial forces |
—
|
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: revolt suppressed by colonial forces | Statement: [Bussa, revoltOutcome, revolt suppressed by colonial forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revoltOutcome Context triple: [Bussa, revoltOutcome, revolt suppressed by colonial forces]
-
A.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
B.
notableRevolt
Indicates a significant uprising or rebellion in which the subject played an important or historically notable role.
-
C.
uprising
Indicates a collective act of resistance or rebellion by a group against an established authority or ruling power.
-
D.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
E.
postRevoltStatus
chosen
Indicates the condition or state of an entity after a revolt or uprising has occurred.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.