Triple

T20675986
Position Surface form Disambiguated ID Type / Status
Subject Lahhentagge Manor E508160 entity
Predicate locatedIn P40 FINISHED
Object Saare County NE NERFINISHED

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: Saare County | Statement: [Lahhentagge Manor, locatedIn, Saare County]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saare County
Context triple: [Lahhentagge Manor, locatedIn, Saare County]
  • A. Saare County chosen
    Saare County is a county in western Estonia that encompasses the islands of Saaremaa and several smaller islands in the Baltic Sea.
  • B. Valga County
    Valga County is a rural administrative region in southern Estonia known for its forests, lakes, and the twin town of Valga–Valka on the Estonian-Latvian border.
  • C. Lääne County
    Lääne County is a coastal administrative region in western Estonia known for its historic town of Haapsalu and its Baltic Sea shoreline.
  • D. Jõgeva County
    Jõgeva County is an administrative region in eastern Estonia known for its agricultural landscapes, small towns, and cold winter temperatures.
  • E. Hiiu County
    Hiiu County is an administrative region of Estonia encompassing the island of Hiiumaa and its surrounding islets in the Baltic Sea.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4c1164881909a3bf1e3ddb2bc32 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6b5cf18b48190be6995e197946517 completed April 20, 2026, 11:25 p.m.
Created at: April 16, 2026, 11:44 a.m.