Triple

T23313881
Position Surface form Disambiguated ID Type / Status
Subject Zagorje E590651 entity
Predicate hasSettlement P1068 FINISHED
Object Zabok 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: Zabok | Statement: [Zagorje, hasSettlement, Zabok]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zabok
Context triple: [Zagorje, hasSettlement, Zabok]
  • A. Zabok chosen
    Zabok is a small town in northern Croatia known for its role as a local administrative, commercial, and transport center in the Krapina-Zagorje County.
  • B. Rabsztyn
    Rabsztyn is a village in southern Poland known for the ruins of its medieval castle, which is part of the historic Trail of the Eagles' Nests.
  • C. Bzura
    Bzura is a river in central Poland known for its historical significance, including being the site of a major World War II battle.
  • D. Zbyszko
    Zbyszko is a Polish given name, traditionally used as a diminutive or variant of Zbigniew and known from medieval and literary contexts.
  • E. Kuków
    Kuków is a village in southern Poland located within the administrative district of Gmina Stryszawa in the Lesser Poland 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_69e25d1d32188190948eb76909d1dcc3 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1977ee5d08190a9519d7867d6bef9 completed April 29, 2026, 5:30 a.m.
Created at: April 17, 2026, 5:06 p.m.