Triple

T32032205
Position Surface form Disambiguated ID Type / Status
Subject Ishak E817995 entity
Predicate associatedWithArmamentContext P33241 FINISHED
Object machine-gun armed fighter 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: machine-gun armed fighter | Statement: [Ishak, associatedWithArmamentContext, machine-gun armed fighter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithArmamentContext
Context triple: [Ishak, associatedWithArmamentContext, machine-gun armed fighter]
  • A. associatedWithWeapon chosen
    Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given context.
  • B. associatedWithMissile
    Indicates a relationship in which an entity is connected or linked to a missile, such as through ownership, use, design, deployment, or operational involvement.
  • C. weaponSystemAssociatedWith
    Indicates that one entity is functionally or organizationally connected to a particular weapon system, such as by using, supporting, or being part of that system.
  • D. refersToArmamentRole
    Indicates that one entity specifies or denotes the armament-related role or function associated with another entity.
  • E. armamentConfiguration
    Indicates how weapons or armaments are arranged, equipped, or configured on an entity in a given 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_69f348fbc8148190b3c0f95d4772b153 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a037c894b488190bcbec2eccaff4a01 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379eaa540819095a1c5d9f3513f9b completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 12:18 a.m.