Triple

T11165920
Position Surface form Disambiguated ID Type / Status
Subject Morungen E264158 entity
Predicate hasCurrentName P1213 FINISHED
Object Morąg E220539 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: Morąg | Statement: [Morungen, hasCurrentName, Morąg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Morąg
Context triple: [Morungen, hasCurrentName, Morąg]
  • A. Morąg chosen
    Morąg is a small historic town in northern Poland known for its lakeside surroundings and location within the Warmian-Masurian Voivodeship.
  • B. Orlovika
    Orlovika is an alternative name for the Orlov Revolt, an 18th-century Greek uprising against Ottoman rule encouraged by Russia during the Russo-Turkish War.
  • C. Ustronie Morskie
    Ustronie Morskie is a seaside resort village on the Baltic coast of northwestern Poland, known for its beaches and tourism.
  • D. Morskie Oko
    Morskie Oko is a famous glacial lake in the Tatra Mountains of southern Poland, renowned for its scenic alpine setting and popularity as a hiking destination.
  • E. Шхара
    Шхара — одна из самых высоких вершин Кавказа и высшая точка Грузии, расположенная в массиве Большого Кавказского хребта.
  • 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_69e463945e40819087c6bdbc322a6d54 completed April 19, 2026, 5:09 a.m.
Created at: April 8, 2026, 9:29 p.m.