Triple

T4741790
Position Surface form Disambiguated ID Type / Status
Subject Ohrid E105259 entity
Predicate nearbyCity P350 FINISHED
Object Struga E400598 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: Struga | Statement: [Ohrid, nearbyCity, Struga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Struga
Context triple: [Ohrid, nearbyCity, Struga]
  • A. Struga chosen
    Struga is a town in southwestern North Macedonia known for its location on the shores of Lake Ohrid and its annual international poetry festival.
  • B. Morača
    Morača is a major river in Montenegro that flows through the capital city of Podgorica before emptying into Lake Skadar.
  • C. Brda
    Brda is a river in northern Poland that flows through the Pomeranian region and is known for its scenic landscapes and popular kayaking routes.
  • D. Brda
    Brda is a picturesque wine-growing municipality in western Slovenia, renowned for its rolling hills, vineyards, and traditional villages near the Italian border.
  • E. Sagarejo
    Sagarejo is a town in eastern Georgia that serves as an important local center in the Kakheti wine-producing region.
  • 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_69bd43ef87a48190a5bc3600711aa032 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64a7153881909eac451fc7566d25 completed March 20, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a28ca648190a44d178826926812 completed March 21, 2026, 6:26 a.m.
Created at: March 20, 2026, 1:19 p.m.