Triple

T23758283
Position Surface form Disambiguated ID Type / Status
Subject Battle of Longewala E587178 entity
Predicate attackingForceEquipment P153850 FINISHED
Object Pakistani M4 Sherman tanks 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: Pakistani M4 Sherman tanks | Statement: [Battle of Longewala, attackingForceEquipment, Pakistani M4 Sherman tanks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: attackingForceEquipment
Context triple: [Battle of Longewala, attackingForceEquipment, Pakistani M4 Sherman tanks]
  • A. enemyMilitaryAsset
    Indicates that one entity is a military asset belonging to or controlled by an enemy force relative to the other entity.
  • B. missionEquipment
    Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
  • C. isMilitaryAssetOf
    Indicates that something functions as a military resource, equipment, or facility that belongs to, is controlled by, or is used by a particular entity.
  • D. warfareCapability
    Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
  • E. weaponCapability
    Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
  • 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_69e2490a0eec81908cdef8a862828d7a completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1bdaf52848190b034208de4c4e01a completed April 29, 2026, 8:13 a.m.
PD Predicate disambiguation batch_69f155f79e34819080f9ddb972b34deb completed April 29, 2026, 12:51 a.m.
PDg Predicate description generation batch_69f15ed138f88190a8ae555422978908 completed April 29, 2026, 1:28 a.m.
Created at: April 17, 2026, 7:14 p.m.