Triple

T1858340
Position Surface form Disambiguated ID Type / Status
Subject SVR E41755 entity
Predicate hasContinuityWith P26885 FINISHED
Object Soviet-era intelligence practices 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: Soviet-era intelligence practices | Statement: [SVR, hasContinuityWith, Soviet-era intelligence practices]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasContinuityWith
Context triple: [SVR, hasContinuityWith, Soviet-era intelligence practices]
  • A. continuityFrom chosen
    Indicates that one entity continues, extends, or proceeds directly from another in a seamless or unbroken manner.
  • B. symbolicContinuity
    Indicates that there is a consistent, ongoing use or preservation of the same symbols or symbolic forms across time, contexts, or instances.
  • C. continuedBy
    Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
  • D. laterIdentityContinuityWith
    Indicates that an entity at a later time is considered the same continuing individual or identity as an entity at an earlier time.
  • E. continuityStatus
    Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
  • 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_69a8864a83848190a4ec02721306c511 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb231de14819091da3a20ed03c430 completed March 7, 2026, 5:05 a.m.
PD Predicate disambiguation batch_69abafde4598819099d8229128348fd3 completed March 7, 2026, 4:55 a.m.
Created at: March 4, 2026, 7:33 p.m.