Triple

T4182339
Position Surface form Disambiguated ID Type / Status
Subject Saint Petersburg Oblast E88221 entity
Predicate hasHistoricTown P847 FINISHED
Object Vyborg E29736 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: Vyborg | Statement: [Saint Petersburg Oblast, hasHistoricTown, Vyborg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vyborg
Context triple: [Saint Petersburg Oblast, hasHistoricTown, Vyborg]
  • A. Vyborg chosen
    Vyborg is a historic port city in northwestern Russia near the Finnish border, known for its medieval castle and long-contested status between Sweden, Finland, and Russia.
  • B. Kotka
    Kotka is a coastal city in southeastern Finland on the Gulf of Finland, known as an important port and maritime center.
  • C. Vaasa
    Vaasa is a coastal city in western Finland known for its maritime heritage, bilingual Finnish-Swedish culture, and role as a regional economic and educational center.
  • D. Jakobstad
    Jakobstad is a coastal town and municipality in western Finland known for its bilingual (Finnish and Swedish) heritage and maritime history.
  • E. Viipuri
    Viipuri is the Finnish name for Vyborg, a historically significant city and former Finnish cultural center now located in Russia near the Finnish border.
  • 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_69aed9477e8c81908bcb862d2db55b1d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af0305e2e88190a51f176f8534f1f9 completed March 9, 2026, 5:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5b766915c81909b778ce391e43c22 completed March 14, 2026, 7:30 p.m.
Created at: March 9, 2026, 3:45 p.m.