Triple

T10546849
Position Surface form Disambiguated ID Type / Status
Subject Bochum E248839 entity
Predicate twinTown P1072 FINISHED
Object Donezk E110135 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: Donezk | Statement: [Bochum, twinTown, Donezk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Donezk
Context triple: [Bochum, twinTown, Donezk]
  • A. Dnipro
    Dnipro is one of Ukraine’s largest industrial and cultural centers, located on the Dnieper River in the central-eastern part of the country.
  • B. Donetsk chosen
    Donetsk is a major industrial city in eastern Ukraine, historically known for its coal mining and steel production.
  • C. Kremenchuk
    Kremenchuk is an industrial city in central Ukraine on the Dnieper River, historically significant as a major transport and strategic hub.
  • D. Dniprodzerzhynsk
    Dniprodzerzhynsk (now officially called Kamianske) is an industrial city in central Ukraine known for its heavy industry and metallurgical enterprises along the Dnieper River.
  • E. Oleksandriia
    Oleksandriia is a city in central Ukraine known as an industrial and transport hub within the Kirovohrad region.
  • 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_69d381c733c08190ab1dd6239f5f34ae completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d526d20ef48190ab9f70d4ce5f2a11 completed April 7, 2026, 3:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69e2d65fc0948190af4356fc9f5004bb completed April 18, 2026, 12:54 a.m.
Created at: April 6, 2026, 12:33 p.m.