Triple

T26198742
Position Surface form Disambiguated ID Type / Status
Subject Lachit Borphukan E655174 entity
Predicate battleTactics P30685 FINISHED
Object use of small, maneuverable boats 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: use of small, maneuverable boats | Statement: [Lachit Borphukan, battleTactics, use of small, maneuverable boats]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: battleTactics
Context triple: [Lachit Borphukan, battleTactics, use of small, maneuverable boats]
  • A. militaryTacticsUsed chosen
    Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
  • B. militaryTacticsFaced
    Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
  • C. battleSystem
    Indicates a relationship where entities are engaged in or governed by a structured combat or conflict-resolution mechanism.
  • D. battleTarget
    Indicates that one entity is the chosen opponent or objective that another entity is engaging or intends to engage in battle.
  • E. tacticalStyle
    Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
  • 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_69ee5b48236c81908fe385b6afc4f60b completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f60cd8c4608190bdf0cc6142264239 completed May 2, 2026, 2:40 p.m.
PD Predicate disambiguation batch_69f602d07590819085ac34b189613104 completed May 2, 2026, 1:57 p.m.
Created at: April 26, 2026, 8:47 p.m.