Triple

T15856054
Position Surface form Disambiguated ID Type / Status
Subject Sozh River E384458 entity
Predicate majorCityOnRiver P316 FINISHED
Object Cherykaw E958988 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: Cherykaw | Statement: [Sozh River, majorCityOnRiver, Cherykaw]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cherykaw
Context triple: [Sozh River, majorCityOnRiver, Cherykaw]
  • A. Cherykaw chosen
    Cherykaw is a small town in eastern Belarus known for its location on the Sozh River and its heavy damage during World War II.
  • B. Chorokhi
    Chorokhi is a river in the South Caucasus that flows from northeastern Turkey into southwestern Georgia before emptying into the Black Sea.
  • C. Chakesar
    Chakesar is a town and administrative center in Pakistan’s Khyber Pakhtunkhwa province, known for its mountainous terrain and agricultural surroundings.
  • D. Ko Chorakhe
    Ko Chorakhe is a small island located within Thailand’s Chumphon Archipelago, known for its coastal scenery and marine environment.
  • E. Chakosi
    Chakosi is a Gur language spoken primarily by the Chakosi (Anufo) people in parts of Ghana, Togo, and Benin.
  • 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_69d86da422088190aac39e32e6c68429 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e14cb08bd081908af2120eb2925441 completed April 16, 2026, 8:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa14c1e508190a182db216cc4e326 completed May 9, 2026, 9:04 p.m.
Created at: April 10, 2026, 4:50 a.m.