Triple

T11165924
Position Surface form Disambiguated ID Type / Status
Subject Morungen E264158 entity
Predicate locatedNorthOf P305 FINISHED
Object Ostróda E376925 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: Ostróda | Statement: [Morungen, locatedNorthOf, Ostróda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ostróda
Context triple: [Morungen, locatedNorthOf, Ostróda]
  • A. Ostróda chosen
    Ostróda is a town in northern Poland known for its lakeside setting, tourism, and role as a local economic and cultural center.
  • B. Olsztyn
    Olsztyn is a historic city in northern Poland known for its medieval architecture, lakes, and role as the capital of the Warmian-Masurian Voivodeship.
  • C. Olsztynek
    Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
  • D. Ostrołęka
    Ostrołęka is a town in east-central Poland known for its historical role in the Napoleonic Wars and as a local industrial and administrative center.
  • E. Świdwin
    Świdwin is a historic town in northwestern Poland, known for its medieval castle and location in the West Pomeranian Voivodeship.
  • 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e887293081909830852000d533fa completed April 9, 2026, 5:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd4c1d31048190ab0a8d8e00515211 completed May 8, 2026, 2:36 a.m.
Created at: April 8, 2026, 9:29 p.m.