Triple

T17249369
Position Surface form Disambiguated ID Type / Status
Subject Battle of Vyborg Bay E418708 entity
Predicate location P40 FINISHED
Object Vyborg Bay E939953 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 Bay | Statement: [Battle of Vyborg Bay, location, Vyborg Bay]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vyborg Bay
Context triple: [Battle of Vyborg Bay, location, Vyborg Bay]
  • A. Vyborg Bay chosen
    Vyborg Bay is a coastal inlet of the Gulf of Finland in the Baltic Sea, known for its scenic archipelago, historic port city of Vyborg, and strategic maritime location between Russia and Finland.
  • B. Tallinn Bay
    Tallinn Bay is a coastal bay in northern Estonia on the Gulf of Finland, forming the maritime setting for the city of Tallinn and its surrounding islands.
  • C. Tuapse Bay
    Tuapse Bay is a coastal inlet on the northeastern shore of the Black Sea, serving as the maritime setting for the Russian port city of Tuapse.
  • D. Onega Bay
    Onega Bay is a large southern inlet of Russia’s White Sea, known for its numerous islands, shallow waters, and importance to regional fishing and navigation.
  • E. Töölönlahti Bay
    Töölönlahti Bay is a scenic urban bay in central Helsinki, Finland, surrounded by parks, cultural landmarks, and walking paths.
  • 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_69d886d9ab108190b70edd8d17aa1204 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42e2636f48190b29548ff80402bef completed April 19, 2026, 1:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0170f96e548190be92846e072118f9 completed May 11, 2026, 6:02 a.m.
Created at: April 10, 2026, 5:39 a.m.