Triple
T686122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nana Sahib |
E13286
|
entity |
| Predicate | causeOfRebellion |
P694
|
FINISHED |
| Object | annulment of his pension by the British |
—
|
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: annulment of his pension by the British | Statement: [Nana Sahib, causeOfRebellion, annulment of his pension by the British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfRebellion Context triple: [Nana Sahib, causeOfRebellion, annulment of his pension by the British]
-
A.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
-
B.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
C.
uprising
Indicates a collective act of resistance or rebellion by a group against an established authority or ruling power.
-
D.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
casusBelliFor
Indicates that one entity serves as the justification or cause for another entity to initiate conflict, often war or hostilities.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d2048d48190ab99ab59accb6909 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.