Triple

T1454623
Position Surface form Disambiguated ID Type / Status
Subject Strategic Arms Limitation Talks E31369 entity
Predicate aimedToLimit P28788 FINISHED
Object strategic offensive arms 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: strategic offensive arms | Statement: [Strategic Arms Limitation Talks, aimedToLimit, strategic offensive arms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimedToLimit
Context triple: [Strategic Arms Limitation Talks, aimedToLimit, strategic offensive arms]
  • A. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • B. triedToAvoid
    Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
  • C. aimsToMeasure
    Indicates that one entity is intended or designed to quantify, assess, or evaluate another entity or property.
  • D. aimsToBalance
    Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
  • E. hasLimitation
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • 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_69a499171a28819085b993a3ac78e363 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c57fead881909a47188ce7312406 completed March 1, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69a4c47cdbd0819092022344a2f4ad7b completed March 1, 2026, 10:58 p.m.
PDg Predicate description generation batch_69a4c55508948190922aee3230a4323e completed March 1, 2026, 11:01 p.m.
Created at: March 1, 2026, 8 p.m.