Triple

T5527101
Position Surface form Disambiguated ID Type / Status
Subject Vladimir Tatlin E144946 entity
Predicate givenName P17 FINISHED
Object Vladimir E56831 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: Vladimir | Statement: [Vladimir Tatlin, givenName, Vladimir]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vladimir
Context triple: [Vladimir Tatlin, givenName, Vladimir]
  • A. Vladimir chosen
    Vladimir is a common Russian male given name of Slavic origin, historically associated with rulers and notably borne by Russian president Vladimir Putin.
  • B. Vladimir
    Vladimir is a historic Russian city east of Moscow, known as one of the medieval capitals of Russia and a key center of the Golden Ring.
  • C. Vladislav
    Vladislav is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
  • D. Vsevolod
    Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
  • E. Lzhedmitry I
    Lzhedmitry I is the Russian name for False Dmitry I, the first and most prominent of the pretenders who claimed the Russian throne during the Time of Troubles in the early 17th century.
  • 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_69c008f873a481909b4d9f7e2db3c37d completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f8a34a48190bcbd0036f79246a9 completed March 22, 2026, 4:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69c027fe1c508190b95b7b5bda96a32d completed March 22, 2026, 5:33 p.m.
Created at: March 22, 2026, 3:34 p.m.