Triple

T10380947
Position Surface form Disambiguated ID Type / Status
Subject Arseny Tarkovsky E244638 entity
Predicate givenName P17 FINISHED
Object Arseny
Arseny is a masculine given name of Russian origin, historically borne by several notable figures in literature, art, and public life.
 E897562 NE FINISHED

How this triple was built (4 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: Arseny | Statement: [Arseny Tarkovsky, givenName, Arseny]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Arseny
Context triple: [Arseny Tarkovsky, givenName, Arseny]
  • A. Grigory
    Grigory is a masculine given name of Russian origin, historically borne by notable figures such as statesman and nobleman Grigory Orlov.
  • 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. Ratmir
    Ratmir is a Tatar prince who appears as a gallant yet ultimately reformed seducer in Alexander Pushkin’s narrative poem "Ruslan and Ludmila."
  • D. Anatoly
    Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • E. 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.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Arseny
Triple: [Arseny Tarkovsky, givenName, Arseny]
Generated description
Arseny is a masculine given name of Russian origin, historically borne by several notable figures in literature, art, and public life.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Arseny
Target entity description: Arseny is a masculine given name of Russian origin, historically borne by several notable figures in literature, art, and public life.
  • A. Grigory
    Grigory is a masculine given name of Russian origin, historically borne by notable figures such as statesman and nobleman Grigory Orlov.
  • 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. Ratmir
    Ratmir is a Tatar prince who appears as a gallant yet ultimately reformed seducer in Alexander Pushkin’s narrative poem "Ruslan and Ludmila."
  • D. Anatoly
    Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • E. 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.
  • F. None of above. chosen

Provenance (5 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_69d381b3e328819094b23b8edcd29b5a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e9921fa48190a874aa9a9e385b97 completed April 7, 2026, 11:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69e343cd76448190b0583cc15005ac9d completed April 18, 2026, 8:41 a.m.
NEDg Description generation batch_69e34fb556648190909c403f5b7709f2 completed April 18, 2026, 9:32 a.m.
NED2 Entity disambiguation (via description) batch_69e358f860f08190bfd10519ff3806aa completed April 18, 2026, 10:12 a.m.
Created at: April 6, 2026, 12:03 p.m.