Triple

T6890674
Position Surface form Disambiguated ID Type / Status
Subject Petr E159035 entity
Predicate hasVariant P455 FINISHED
Object Pyotr E78424 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: Pyotr | Statement: [Petr, hasVariant, Pyotr]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pyotr
Context triple: [Petr, hasVariant, Pyotr]
  • A. Pyotr chosen
    Pyotr is the Russian given name of Peter Kropotkin, the influential 19th-century anarchist philosopher, geographer, and revolutionary.
  • B. Pyotr Bark
    Pyotr Bark was a Russian statesman and financier who served as the last Minister of Finance of the Russian Empire before the 1917 revolution.
  • C. Pyotr Mikhailov
    Pyotr Mikhailov was the alias used by Tsar Peter the Great of Russia when he traveled incognito during the Grand Embassy to Western Europe in 1697–1698.
  • D. Dmitry Ivanovich
    Dmitry Ivanovich was a late 15th-century Russian prince and one-time heir apparent to the throne of Muscovy during the reign of his grandfather Ivan III.
  • E. Fyodor
    Fyodor is a masculine given name of Russian origin, most famously borne by the novelist Fyodor Dostoevsky.
  • 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_69c6883568c8819081db6407e892cccc completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d92d45f08190a730b3842c95b521 completed March 27, 2026, 7:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7bf709c4c819090c35eb41f46f5d2 completed March 28, 2026, 11:45 a.m.
Created at: March 27, 2026, 2:24 p.m.