Triple

T615887
Position Surface form Disambiguated ID Type / Status
Subject Wilno E14402 entity
Predicate hasAlternativeName P39 FINISHED
Object Vilnius E14402 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: Vilnius | Statement: [Wilno, hasAlternativeName, Vilnius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vilnius
Context triple: [Wilno, hasAlternativeName, Vilnius]
  • A. Kaunas
    Kaunas is the second-largest city in Lithuania, known as a historic cultural and academic center located at the confluence of the Nemunas and Neris rivers.
  • B. Klaipėda
    Klaipėda is a Lithuanian port city on the Baltic Sea known as the country’s main maritime gateway and a key regional transport and industrial hub.
  • C. Riga
    Riga is the capital and largest city of Latvia, a historic cultural and economic hub on the Baltic Sea known for its Art Nouveau architecture and significant port.
  • D. Wilno chosen
    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. 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.
  • 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_69a4934b17c881909ace8270e8ddd202 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49e0b438881909ad515adf7a4eb79 completed March 1, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a563c40fbc81908b117bc6139507d2 completed March 2, 2026, 10:17 a.m.
Created at: March 1, 2026, 7:35 p.m.