Triple

T14445122
Position Surface form Disambiguated ID Type / Status
Subject Holy Hill E358184 entity
Predicate near P350 FINISHED
Object Dzyarzhynsk E391527 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: Dzyarzhynsk | Statement: [Holy Hill, near, Dzyarzhynsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dzyarzhynsk
Context triple: [Holy Hill, near, Dzyarzhynsk]
  • A. Dzyarzhynsk chosen
    Dzyarzhynsk is a town in Belarus known for its proximity to Dzyarzhynskaya Hara, the country’s highest point.
  • B. Kolodiazhne
    Kolodiazhne is a village in northwestern Ukraine known for being closely associated with the life and creative work of the renowned poet Lesya Ukrainka.
  • C. Dzerzhinsk
    Dzerzhinsk is a major industrial city in western Russia known for its large chemical manufacturing sector and associated environmental issues.
  • D. Berdichev
    Berdichev is a historic city in present-day Ukraine, long known as a major center of Jewish life and commerce in Eastern Europe.
  • E. Novogrudok
    Novogrudok is a historic town in western Belarus known as one of the early political centers of the Grand Duchy of Lithuania.
  • 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_69d82794dfa081909b9134ad2e32244b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de915e76f481909fe9462f964b5b1c completed April 14, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8aa904c08190b33796b832aa100f completed May 8, 2026, 7:03 a.m.
Created at: April 10, 2026, 1:19 a.m.