Triple

T12722465
Position Surface form Disambiguated ID Type / Status
Subject R-9 missile E304018 entity
Predicate armsControlRelevance P88437 FINISHED
Object early strategic arms context 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: early strategic arms context | Statement: [R-9 missile, armsControlRelevance, early strategic arms context]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: armsControlRelevance
Context triple: [R-9 missile, armsControlRelevance, early strategic arms context]
  • A. armsControlSignificance chosen
    Indicates the extent to which an action, event, or agreement has importance or impact within the context of arms control efforts and policies.
  • B. armsControl
    Indicates a relationship where parties engage in limiting, regulating, or reducing weapons and military capabilities, often through agreements or treaties.
  • C. weaponControl
    Indicates that one entity has authority over, access to, or the ability to direct the use of a weapon associated with another entity.
  • D. aimsToControl
    Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
  • E. refersToArmamentRole
    Indicates that one entity specifies or denotes the armament-related role or function associated with another entity.
  • 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_69d7bdf084148190ab9d513dc0735af4 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d89ea70819098c470344f172167 completed April 10, 2026, 9:37 p.m.
PD Predicate disambiguation batch_69d96403957c81909acdee7bdae71696 completed April 10, 2026, 8:56 p.m.
Created at: April 9, 2026, 5:24 p.m.