Triple

T17766550
Position Surface form Disambiguated ID Type / Status
Subject Anatoly E443521 entity
Predicate hasLatinTransliteration P76738 FINISHED
Object Anatoli 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: Anatoli | Statement: [Anatoly, hasLatinTransliteration, Anatoli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anatoli
Context triple: [Anatoly, hasLatinTransliteration, Anatoli]
  • A. Anatoli
    Anatoli is a small village in Greece that forms part of the Agia municipality in the regional unit of Larissa.
  • B. Anatolii
    Anatolii is a masculine given name, commonly used in Slavic countries as a variant of the name Anatoly.
  • C. Yuryatin
    Yuryatin is a fictional Russian town in Boris Pasternak’s novel "Doctor Zhivago," serving as a key setting in Lara Antipova’s story.
  • D. Tikhon
    Tikhon was the religious name of Patriarch Tikhon of Moscow, the early 20th-century head of the Russian Orthodox Church known for leading it through the turmoil of the Russian Revolution and early Soviet period.
  • E. Anatoly chosen
    Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking 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_69d8b9edf16c8190a59ebd245d378f4f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e485fccb9881908923564bf319f3c1 completed April 19, 2026, 7:36 a.m.
Created at: April 10, 2026, 10:11 a.m.