Triple

T11462831
Position Surface form Disambiguated ID Type / Status
Subject Vilna E271703 entity
Predicate hasAlternativeName P39 FINISHED
Object Vilne 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: Vilne | Statement: [Vilna, hasAlternativeName, Vilne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vilne
Context triple: [Vilna, hasAlternativeName, Vilne]
  • A. Vilna chosen
    Vilna is the historical name for Vilnius, the capital city of Lithuania and a major cultural and political center of the region.
  • B. Volkovysk
    Volkovysk is a historic town in present-day Belarus, known for its centuries-old Jewish community and changing rule under various Eastern European states.
  • C. Alytus
    Alytus is a city in southern Lithuania known as a regional cultural and economic center on the banks of the Nemunas River.
  • D. Budyšin
    Budyšin is the Upper Sorbian name for the historic town of Bautzen in eastern Germany, a cultural center of the Sorbian minority.
  • E. Mitau
    Mitau, historically known as the capital of the Duchy of Courland and Semigallia, is the former German name for the city now called Jelgava in present-day Latvia.
  • 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_69d6aae0c8d881908a5a360c0be3242e completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d822f488248190b9f603cd31c72174 completed April 9, 2026, 10:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5e92a7c2881908d85009a6069b2e4 completed April 20, 2026, 8:51 a.m.
Created at: April 8, 2026, 9:35 p.m.