Triple

T7712442
Position Surface form Disambiguated ID Type / Status
Subject Grigory Semyonov E174792 entity
Predicate givenName P17 FINISHED
Object Grigory E174792 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: Grigory | Statement: [Grigory Semyonov, givenName, Grigory]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Grigory
Context triple: [Grigory Semyonov, givenName, Grigory]
  • A. Grigory Rapota
    Grigory Rapota is a Russian statesman and diplomat who has held several high-ranking government posts, including serving as a presidential plenipotentiary envoy.
  • B. Grigory Spiridov
    Grigory Spiridov was a prominent 18th-century Russian admiral best known for his leadership in the Russo-Turkish War, particularly at the Battle of Chesma.
  • C. Gavril
    Gavril is a masculine given name, commonly used in Slavic and Eastern European cultures, that derives from the Hebrew name Gabriel.
  • D. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • E. Grigory Semyonov chosen
    Grigory Semyonov was a Russian Cossack military leader and prominent anti-Bolshevik figure who commanded White forces in Siberia and the Russian Far East during the Russian Civil War.
  • 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_69c6995c463c8190a14458036249d419 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c702c96e388190898165f84d646c0e completed March 27, 2026, 10:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c922ac9c108190a9f00381d951b20d completed March 29, 2026, 1:01 p.m.
Created at: March 27, 2026, 4:04 p.m.