Triple

T10109657
Position Surface form Disambiguated ID Type / Status
Subject Александр Невский E218207 entity
Predicate patronymic P7966 FINISHED
Object Ярославич E751899 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: Ярославич | Statement: [Александр Невский, patronymic, Ярославич]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ярославич
Context triple: [Александр Невский, patronymic, Ярославич]
  • A. Yaroslav chosen
    Yaroslav is a given name of Slavic origin, commonly used in Eastern Europe and associated with several historical rulers and notable figures.
  • B. Vsevolodovich
    Vsevolodovich is the patronymic indicating that Vladimir II Monomakh was the son of Vsevolod, a ruler of Kievan Rus'.
  • C. Vyacheslav Yaroslavich
    Vyacheslav Yaroslavich was a lesser-known 11th-century Rus' prince, one of the sons of Grand Prince Yaroslav the Wise of Kiev.
  • D. Vsevolod Mstislavich
    Vsevolod Mstislavich was a 12th-century Rurikid prince known for his turbulent reigns in Novgorod and later in Pskov, where he became the city’s first independent prince.
  • E. Vladislav
    Vladislav 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 (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_69ca83da93fc8190b54e44bc2b34857c completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cdd0cdb3c88190a74f75bf865664f3 completed April 2, 2026, 2:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2cc1805d08190bc39aadf1e84a569 completed April 5, 2026, 8:54 p.m.
Created at: March 30, 2026, 9:03 p.m.