Triple

T31400131
Position Surface form Disambiguated ID Type / Status
Subject Sir Samuel Browne E800973 entity
Predicate VCActionConflict P171831 FINISHED
Object Indian Rebellion of 1857 NE NERFINISHED

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: Indian Rebellion of 1857 | Statement: [Sir Samuel Browne, VCActionConflict, Indian Rebellion of 1857]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: VCActionConflict
Context triple: [Sir Samuel Browne, VCActionConflict, Indian Rebellion of 1857]
  • A. ledToConflict
    Indicates that one event, action, or condition caused or significantly contributed to the emergence or escalation of a conflict between parties.
  • B. ledConflict
    Indicates that one entity was primarily responsible for initiating, directing, or driving a particular conflict involving another entity or group.
  • C. wonConflict
    Indicates that one entity has prevailed over another in a conflict, contest, or struggle.
  • D. facesConflictWith
    Indicates that one entity is in opposition, dispute, or contention with another, involving incompatible goals, interests, or actions.
  • E. subConflict
    Indicates that one conflict is a component, phase, or subordinate part of a larger overarching conflict.
  • F. None of above. chosen

Provenance (4 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_69f224ea9998819086ae2e4f4f4091c8 completed April 29, 2026, 3:34 p.m.
NER Named-entity recognition batch_69f6a5f71b2c8190aade8a83f465be0c completed May 3, 2026, 1:33 a.m.
PD Predicate disambiguation batch_69f69fe66df08190958558d63ee623d9 completed May 3, 2026, 1:07 a.m.
PDg Predicate description generation batch_69f6a5f656ec81909e02b0b873303adf completed May 3, 2026, 1:33 a.m.
Created at: April 29, 2026, 9:19 p.m.