Triple

T34747929
Position Surface form Disambiguated ID Type / Status
Subject Azov Regiment E1001687 entity
Predicate integratedIntoStateForces P37308 FINISHED
Object November 2014 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: November 2014 | Statement: [Azov Regiment, integratedIntoStateForces, November 2014]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: integratedIntoStateForces
Context triple: [Azov Regiment, integratedIntoStateForces, November 2014]
  • A. includedForcesFrom chosen
    Indicates that one set of forces is derived from, or incorporated within, another set of forces.
  • B. usesForcesFrom
    Indicates that one entity applies or derives physical forces from another entity as part of its operation or behavior.
  • C. enteredIntoForceForInitialStates
    Indicates that a legal agreement, treaty, or instrument has become legally binding and effective for the original group of states that first adopted or ratified it.
  • D. componentForces
    Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
  • E. governingForceOf
    Indicates that one entity functions as the primary controlling or directing influence over another entity’s behavior, state, or dynamics.
  • 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_69f76db0367081909b57c50a7fb03025 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77ffa6b68819090257fed3802c239 completed May 3, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69f7795978c481909e152cd1bd02dd07 completed May 3, 2026, 4:35 p.m.
Created at: May 3, 2026, 3:59 p.m.