Triple

T4744668
Position Surface form Disambiguated ID Type / Status
Subject Vilnius E105330 entity
Predicate historicalName P65 FINISHED
Object Wilna E271703 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: Wilna | Statement: [Vilnius, historicalName, Wilna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wilna
Context triple: [Vilnius, historicalName, Wilna]
  • A. 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.
  • B. Vilna chosen
    Vilna is the historical name for Vilnius, the capital city of Lithuania and a major cultural and political center of the region.
  • C. 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.
  • D. Elbing
    Elbing is a historic Baltic port city, now known as Elbląg in Poland, that played a notable role in medieval trade as part of the Hanseatic commercial network.
  • E. Polotsk
    Polotsk is one of the oldest cities in Belarus, historically a major political, cultural, and religious center of the medieval East Slavic world.
  • 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_69bd43ef87a48190a5bc3600711aa032 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64aa72c0819082ede0f531d75e65 completed March 20, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69be67be28308190ae428035647fc227 completed March 21, 2026, 9:41 a.m.
Created at: March 20, 2026, 1:19 p.m.