Triple

T17416901
Position Surface form Disambiguated ID Type / Status
Subject Skvyra Uyezd E423512 entity
Predicate namedAfter P63 FINISHED
Object Skvyra 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: Skvyra | Statement: [Skvyra Uyezd, namedAfter, Skvyra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skvyra
Context triple: [Skvyra Uyezd, namedAfter, Skvyra]
  • A. Skvyra chosen
    Skvyra is a town in central Ukraine historically known for its significant Jewish community and cultural life in the 19th and early 20th centuries.
  • B. Prystaiko
    Prystaiko is the surname of Vadym Prystaiko, a Ukrainian diplomat and former Minister of Foreign Affairs.
  • C. Ruklys
    Ruklys was a son of King Mindaugas of Lithuania, known primarily from medieval historical records of the Lithuanian royal family.
  • D. Vardzia
    Vardzia is a medieval cave monastery complex in southern Georgia, renowned for its extensive rock-cut dwellings and frescoed church.
  • E. Velnias
    Velnias is a chthonic deity in Baltic paganism associated with the underworld, the dead, and often trickster-like or demonic qualities.
  • 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e44232ecdc8190ac8958c1780fea19 completed April 19, 2026, 2:47 a.m.
Created at: April 10, 2026, 5:46 a.m.