Triple

T952815
Position Surface form Disambiguated ID Type / Status
Subject Tallinn E20558 entity
Predicate hasDistrict P459 FINISHED
Object Põhja-Tallinn E114152 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: Põhja-Tallinn | Statement: [Tallinn, hasDistrict, Põhja-Tallinn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Põhja-Tallinn
Context triple: [Tallinn, hasDistrict, Põhja-Tallinn]
  • A. Vyborg
    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. Tallinn
    Tallinn is the capital and largest city of Estonia, a historic Baltic Sea port known for its well-preserved medieval Old Town and strategic maritime location.
  • C. Tartu
    Tartu is Estonia’s second-largest city and a historic cultural and intellectual center, best known as the country’s main university town.
  • D. Mustamäe chosen
    Mustamäe is a residential district in the western part of Tallinn, Estonia, known for its Soviet-era apartment blocks and proximity to universities and technology hubs.
  • E. Lappeenranta
    Lappeenranta is a city in southeastern Finland near the Russian border, known for its lakeside location on Saimaa and its role as a regional commercial and educational 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_69a493b0f2fc81908cd227480a5356a1 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b3d8f2e0819097554a301f8aa70f completed March 1, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac1cd569a4819082687be40145331e completed March 7, 2026, 12:40 p.m.
Created at: March 1, 2026, 7:40 p.m.