Triple

T1424512
Position Surface form Disambiguated ID Type / Status
Subject Palashi E30298 entity
Predicate battleConsequence P19109 FINISHED
Object beginning of British political control in Bengal 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: beginning of British political control in Bengal | Statement: [Palashi, battleConsequence, beginning of British political control in Bengal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: battleConsequence
Context triple: [Palashi, battleConsequence, beginning of British political control in Bengal]
  • A. battleOccurred
    Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
  • B. resultOfBattle chosen
    Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
  • C. battleOutcomeRole
    Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
  • D. casualtiesImpact
    Indicates how the number or severity of casualties affects or influences another factor, situation, or outcome.
  • E. tacticalOutcome
    Indicates the specific result or consequence produced by a particular tactic or tactical action in a given situation.
  • 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_69a498fb823c8190a67ce4c4837e641a completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c52e4ed881908d85e0cb9fe851ac completed March 1, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69a4c4752abc8190a33b634c4d6fad28 completed March 1, 2026, 10:57 p.m.
Created at: March 1, 2026, 8 p.m.