Triple

T20381929
Position Surface form Disambiguated ID Type / Status
Subject Arkadyevich E497854 entity
Predicate derivedFrom P909 FINISHED
Object Arkadiy NE NERFINISHED

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: Arkadiy | Statement: [Arkadyevich, derivedFrom, Arkadiy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arkadiy
Context triple: [Arkadyevich, derivedFrom, Arkadiy]
  • A. Arkadi chosen
    Arkadi is a masculine given name of Armenian and Slavic origin, commonly used in Eastern Europe and the Caucasus.
  • B. Arkadyevich
    Arkadyevich is the patronymic of Stepan Arkadyevich Oblonsky, a central socialite and bureaucratic character in Leo Tolstoy’s novel "Anna Karenina."
  • C. Arcadi Gaydamak
    Arcadi Gaydamak is a Russian-Israeli businessman and political figure best known for his controversial role in international arms deals and high-profile legal and financial scandals.
  • D. Leonid
    Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
  • E. Vadim
    Vadim is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4a5b7908190a972e4e7e698ae94 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e678b0ee708190bdbe4aab28a61525 completed April 20, 2026, 7:04 p.m.
Created at: April 16, 2026, 11:27 a.m.