Triple

T2469050
Position Surface form Disambiguated ID Type / Status
Subject Kiev Special Military District E55324 entity
Predicate controlledForcesType P1062 FINISHED
Object ground forces 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: ground forces | Statement: [Kiev Special Military District, controlledForcesType, ground forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controlledForcesType
Context triple: [Kiev Special Military District, controlledForcesType, ground forces]
  • A. controlled
    Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
  • B. forceType chosen
    Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
  • C. controlFrom
    Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
  • D. drivingForce
    Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
  • E. exportControl
    Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
  • 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_69ab49e3622c8190ad22afa2c4fbb807 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd2bc7b5481908b3664495e99f1a4 completed March 7, 2026, 7:24 a.m.
PD Predicate disambiguation batch_69abd0b3ea308190a6d8499c2a542c50 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:44 p.m.