Triple

T563097
Position Surface form Disambiguated ID Type / Status
Subject Lwów E13495 entity
Predicate hasNameInLanguage P15 FINISHED
Object Lwów (Polish) E13495 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: Lwów (Polish) | Statement: [Lwów, hasNameInLanguage, Lwów (Polish)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lwów (Polish)
Context triple: [Lwów, hasNameInLanguage, Lwów (Polish)]
  • A. Lwów chosen
    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.
  • B. Lutsk
    Lutsk is a historic city in northwestern Ukraine, known as the administrative center of Volyn Oblast and one of the region’s oldest cultural and economic hubs.
  • C. Lublin
    Lublin is a historic city in eastern Poland known as a major cultural, academic, and economic center and for its significant role in Polish political history.
  • D. Wilno
    Wilno is the historical Polish name for Vilnius, a major cultural and political center of the region that served as an important city in the interwar Second Polish Republic.
  • E. Tarnów
    Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
  • 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_69a4933edcf08190b35ecfd6014caee6 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49a712bc48190ba298b3c76ab11cc completed March 1, 2026, 7:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4fc7dea048190a5a1472825f6d747 completed March 2, 2026, 2:57 a.m.
Created at: March 1, 2026, 7:32 p.m.