Triple

T380728
Position Surface form Disambiguated ID Type / Status
Subject Valence E8671 entity
Predicate hasTwinTown P919 FINISHED
Object Tver E34278 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: Tver | Statement: [Valence, hasTwinTown, Tver]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tver
Context triple: [Valence, hasTwinTown, Tver]
  • A. Tver chosen
    Tver is a historic city in western Russia, located northwest of Moscow on the Volga River and serving as the administrative center of Tver Oblast.
  • B. Yaroslavl
    Yaroslavl is a historic city in central Russia, located on the Volga River and known as one of the Golden Ring cities famed for its well-preserved medieval architecture and cultural heritage.
  • C. Tver Governorate
    Tver Governorate was an administrative division of the Russian Empire and early Russian SFSR, centered on the city of Tver, that existed from the late 18th to the early 20th century.
  • D. Tsaritsyn
    Tsaritsyn was the original name of the Russian city now known as Volgograd, a major industrial and historical center on the Volga River.
  • E. Voronezh
    Voronezh is a major city in southwestern Russia, situated on the Voronezh River and serving as an important cultural, industrial, and transportation center.
  • 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_69a2e7f47dd08190a4e294ccbbe46cd4 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec2c95088190a603bb1ee076ebd6 completed Feb. 28, 2026, 1:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69a447f8fac481909c4848ca9b789bc3 completed March 1, 2026, 2:06 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.