Triple

T5115499
Position Surface form Disambiguated ID Type / Status
Subject Special Victims Division E115321 entity
Predicate abbreviation P43 FINISHED
Object SVD E115321 NE 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: SVD | Statement: [Special Victims Division, abbreviation, SVD]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SVD
Context triple: [Special Victims Division, abbreviation, SVD]
  • A. SVD chosen
    SVD is the abbreviation for the Special Victims Division, a specialized police unit that investigates sensitive crimes such as sexual offenses and crimes against vulnerable victims.
  • B. sva
    sva is the ISO 639-3 code for the Svan language, a Kartvelian language spoken by the Svan people in the Svaneti region of northwestern Georgia.
  • C. SVR
    SVR is Russia’s primary foreign intelligence service, which succeeded the Soviet-era KGB’s external intelligence functions after the USSR’s dissolution.
  • D. SVR
    SVR is the set of post-nominal letters used to denote recipients of the Order of the White Rose of Finland.
  • E. SVR
    SVR is the ICAO airline designator assigned to Ural Airlines, a Russian commercial air carrier.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd4441d1648190a54a533895041987 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd75ce6044819094166aebf0688665 completed March 20, 2026, 4:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69bebaadfaac8190aa0407196e5c4c20 completed March 21, 2026, 3:35 p.m.
Created at: March 20, 2026, 1:41 p.m.