Triple

T20412969
Position Surface form Disambiguated ID Type / Status
Subject Kuusalu Parish E500634 entity
Predicate borders P224 FINISHED
Object Loksa (town) 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: Loksa (town) | Statement: [Kuusalu Parish, borders, Loksa (town)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loksa (town)
Context triple: [Kuusalu Parish, borders, Loksa (town)]
  • A. Loksa chosen
    Loksa is a small coastal town in northern Estonia known for its shipbuilding history and location on the shores of the Gulf of Finland.
  • B. Lokka
    Lokka is a small village in northern Finland’s Lapland region, known for its proximity to the large Lokka Reservoir and its remote, sparsely populated Arctic environment.
  • C. Lakinsk
    Lakinsk is a small industrial town in western Russia, located in Vladimir Oblast east of Moscow.
  • D. Lochkov
    Lochkov is a district in Prague, Czech Republic, historically known for its geological significance and giving its name to the Lochkovian stage of the Devonian period.
  • E. Laisamis town
    Laisamis town is a small urban center in northern Kenya that serves as an administrative and trading hub for the surrounding arid region.
  • 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_69e0b4a935588190b9446a99b37ced44 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67a417f208190be9bc11650ee0a87 completed April 20, 2026, 7:10 p.m.
Created at: April 16, 2026, 11:30 a.m.