Triple

T371965
Position Surface form Disambiguated ID Type / Status
Subject Eastern Europe E8286 entity
Predicate hasMajorCity P316 FINISHED
Object Minsk E43503 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: Minsk | Statement: [Eastern Europe, hasMajorCity, Minsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Minsk
Context triple: [Eastern Europe, hasMajorCity, Minsk]
  • A. Minsk chosen
    Minsk is the capital and largest city of Belarus, serving as its political, economic, and cultural center.
  • B. Brest (Belarus)
    Brest is a city in southwestern Belarus near the Polish border, known as a major transport hub and for the historic Brest Fortress, a key World War II memorial.
  • C. Vitebsk
    Vitebsk is a historic city in northeastern Belarus known as a major cultural center and the birthplace of artist Marc Chagall.
  • D. Königsberg
    Königsberg was a historic Prussian city on the Baltic Sea, renowned as a major cultural and intellectual center of East Prussia and later known as Kaliningrad.
  • E. Belarus
    Belarus is an Eastern European country known for its flat landscapes, dense forests, and historical ties to both the Soviet Union and the broader Slavic cultural sphere.
  • 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_69a2e7f2ec648190b42bc7db424f8109 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec00785481908551fc3571fcca47 completed Feb. 28, 2026, 1:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3f4da5b2881909f71546e714c7883 completed March 1, 2026, 8:12 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.