Triple

T18814993
Position Surface form Disambiguated ID Type / Status
Subject Sveti Vid-Miholjice E460112 entity
Predicate hasNearbyTown P3883 FINISHED
Object Malinska 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: Malinska | Statement: [Sveti Vid-Miholjice, hasNearbyTown, Malinska]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Malinska
Context triple: [Sveti Vid-Miholjice, hasNearbyTown, Malinska]
  • A. Malinska chosen
    Malinska is a coastal resort town and popular tourist destination on the island of Krk in Croatia, known for its beaches and Mediterranean atmosphere.
  • B. Kraljevica
    Kraljevica is a coastal town in western Croatia known for its historic castles and shipyard on the Adriatic Sea.
  • C. Myślibórz
    Myślibórz is a small historic town in northwestern Poland known for its medieval architecture and picturesque lakes.
  • D. Milonki
    Milonki is a small village located in southern Poland within the administrative district of Gmina Trzyciąż.
  • E. Malše
    Malše is a river in South Bohemia, Czech Republic, that flows through towns including České Budějovice before joining the Vltava River.
  • 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_69d8d398c7d4819091cb2f7e48948aeb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5a3df2d3881909b336d813bbfd0aa completed April 20, 2026, 3:56 a.m.
Created at: April 10, 2026, 11:53 a.m.