Triple

T21353790
Position Surface form Disambiguated ID Type / Status
Subject Bitche canton E526557 entity
Predicate contains P35 FINISHED
Object Lemberg NE NERFINISHED

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: Lemberg | Statement: [Bitche canton, contains, Lemberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lemberg
Context triple: [Bitche canton, contains, Lemberg]
  • A. Lemberg
    Lemberg is a prominent mountain in the Swabian Jura of Baden-Württemberg, Germany, known as the highest peak in that range.
  • B. Lemberg chosen
    Lemberg is a small commune in northeastern France’s Moselle department, situated in the forested, hilly region known as the Pays de Bitche near the German border.
  • C. Lwów
    Lwów is a historic city in Eastern Europe, now known as Lviv in western Ukraine, long recognized as a major cultural and political center of the region.
  • D. Lvov
    Lvov is a Russian noble family name most notably borne by Georgy Lvov, the first head of the Russian Provisional Government after the February Revolution of 1917.
  • E. Czernowitz
    Czernowitz is the former German name of Chernivtsi, a historically multicultural city in Western Ukraine that was once part of the Austro-Hungarian Empire.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee5bac9e1481909121e89f046c77f6 completed April 26, 2026, 6:38 p.m.
Created at: April 16, 2026, 5:05 p.m.