Triple

T5051744
Position Surface form Disambiguated ID Type / Status
Subject Viimsi Parish E113800 entity
Predicate hasSettlement P1068 FINISHED
Object Viimsi E476078 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: Viimsi | Statement: [Viimsi Parish, hasSettlement, Viimsi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Viimsi
Context triple: [Viimsi Parish, hasSettlement, Viimsi]
  • A. Viimsi chosen
    Viimsi is a rapidly developing suburban municipality in northern Estonia, located just northeast of the capital city Tallinn.
  • B. Summajärvi
    Summajärvi is a lake on the Karelian Isthmus in present-day Russia, historically associated with the nearby village of Summa and the Winter War battles fought in the area.
  • C. Vihti
    Vihti is a municipality in southern Finland located within the Uusimaa region, known for its lakes, rural landscapes, and proximity to the Helsinki metropolitan area.
  • D. Kemijoki
    Kemijoki is the longest river in Finland, flowing through Lapland to the Gulf of Bothnia and serving as a major source of hydroelectric power.
  • E. Kalajärvi
    Kalajärvi is a residential district in the northern part of Espoo, Finland, known for its lakeside environment and outdoor recreation areas.
  • 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_69bd443aa1f88190abb992d138f2cf42 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7426fc8081908a8227f73168c235 completed March 20, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69bea483b6cc8190b3b48598a291d708 completed March 21, 2026, 2 p.m.
Created at: March 20, 2026, 1:37 p.m.