Triple

T9976970
Position Surface form Disambiguated ID Type / Status
Subject Yurii Khmelnytsky E196355 entity
Predicate placeOfBirth P1 FINISHED
Object Chyhyryn E191040 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: Chyhyryn | Statement: [Yurii Khmelnytsky, placeOfBirth, Chyhyryn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chyhyryn
Context triple: [Yurii Khmelnytsky, placeOfBirth, Chyhyryn]
  • A. Chyhyryn chosen
    Chyhyryn is a historic Ukrainian town that served as an early political and military center of the Cossack state in the 17th century.
  • B. Nemyriv
    Nemyriv is a historic town in central Ukraine known for its Jewish heritage and role as a regional cultural and economic center.
  • C. Ygerna
    Ygerna is an alternate name for Igraine, the mother of King Arthur in Arthurian legend.
  • D. Courchavon
    Courchavon is a small municipality in the Ajoie region of the canton of Jura in northwestern Switzerland.
  • E. Sassoun
    Sassoun is a mountainous region in historic Western Armenia, famed in Armenian folklore as the homeland of the legendary heroes of the national epic.
  • 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_69ca82eea2b88190a0e511d21a31f386 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb84d0d3c8190b268582bb79c8973 completed April 2, 2026, 12:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69d23de601f0819096004bf60ffa2d2c completed April 5, 2026, 10:48 a.m.
Created at: March 30, 2026, 8:48 p.m.