Triple

T879680
Position Surface form Disambiguated ID Type / Status
Subject Battle of Jhansi E18997 entity
Predicate combatantSide1 P375 FINISHED
Object forces of Jhansi under Rani Lakshmibai 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: forces of Jhansi under Rani Lakshmibai | Statement: [Battle of Jhansi, combatantSide1, forces of Jhansi under Rani Lakshmibai]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: combatantSide1
Context triple: [Battle of Jhansi, combatantSide1, forces of Jhansi under Rani Lakshmibai]
  • A. conflictSide chosen
    Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
  • B. countryOfVictoriousSide
    Indicates the country to which the winning or victorious side in a conflict, competition, or contest belongs.
  • C. alliesInWar
    Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
  • D. countryOfDefeatedSide
    Indicates the country to which the losing or defeated side in a conflict, competition, or confrontation belongs.
  • E. commandersSide
    Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
  • 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_69a4938db1f081909bcd1ad2713b6096 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4acc9d5f4819087afbb75b6ac3dbf completed March 1, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69a4aa8d47c081909b02a53e305ccf7a completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.