Triple

T14504871
Position Surface form Disambiguated ID Type / Status
Subject Yantra Valley E340238 entity
Predicate contains P35 FINISHED
Object Lyaskovets E1016571 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: Lyaskovets | Statement: [Yantra Valley, contains, Lyaskovets]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lyaskovets
Context triple: [Yantra Valley, contains, Lyaskovets]
  • A. Berestovitsa
    Berestovitsa is a Belarusian town known for its strategic location near the border with Poland, serving as an important regional transport and customs point.
  • B. Krolevets
    Krolevets is a small historic city in northeastern Ukraine known for its traditional weaving crafts and location within Sumy Oblast.
  • C. Balabanovo
    Balabanovo is a small town in western Russia known for its industrial enterprises and location along major transportation routes southwest of Moscow.
  • D. Vidnoye
    Vidnoye is a small town in Moscow Oblast, Russia, functioning largely as a residential and industrial satellite of Moscow.
  • E. Loznitsa chosen
    Loznitsa is a small town and municipal center in northeastern Bulgaria known for its agricultural surroundings and local rural character.
  • 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_69d822d9c0408190b9a2b3643e58bb4d completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69de94e25a2481908b8394e9a19f3b64 completed April 14, 2026, 7:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69fda90e1778819095f5ac8848120098 completed May 8, 2026, 9:12 a.m.
Created at: April 10, 2026, 1:21 a.m.