Triple

T18232229
Position Surface form Disambiguated ID Type / Status
Subject Karol Lipiński E436569 entity
Predicate workLocation P7 FINISHED
Object Lviv 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: Lviv | Statement: [Karol Lipiński, workLocation, Lviv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lviv
Context triple: [Karol Lipiński, workLocation, Lviv]
  • A. 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.
  • B. 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.
  • C. Lviv, Ukraine chosen
    Lviv, Ukraine is a historic city in western Ukraine known for its well-preserved medieval architecture, rich cultural life, and role as an intellectual center of the region.
  • D. Rzeszów
    Rzeszów is a major city in southeastern Poland known as an important economic, academic, and cultural center of the region.
  • E. Uzhhorod
    Uzhhorod is a historic city in western Ukraine near the Slovak and Hungarian borders, known for its multicultural heritage and as the administrative center of Zakarpattia Oblast.
  • 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_69d8b9103a8081908bbb0836fef10efd completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4f4b414308190bc7dd8e73c0a362c completed April 19, 2026, 3:28 p.m.
Created at: April 10, 2026, 10:33 a.m.