Triple

T17846656
Position Surface form Disambiguated ID Type / Status
Subject Kfar Saba E445678 entity
Predicate hasSisterCity P919 FINISHED
Object Sderot 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: Sderot | Statement: [Kfar Saba, hasSisterCity, Sderot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sderot
Context triple: [Kfar Saba, hasSisterCity, Sderot]
  • A. Sderot chosen
    Sderot is a small city in southern Israel near the Gaza Strip, known for its frequent exposure to rocket attacks and its resilient community.
  • B. Kissufim
    Kissufim is a small kibbutz in southern Israel near the Gaza border, known for its agricultural community and strategic location.
  • C. Kfar Tavor
    Kfar Tavor is a small agricultural town in northern Israel, known for its historic Jewish settlement roots and its location at the foot of Mount Tabor in the Lower Galilee.
  • D. Kiryat Gat
    Kiryat Gat is a city in south-central Israel known for its industrial zones, high-tech facilities, and location between the coastal plain and the Negev desert.
  • E. Kiryat Shmona
    Kiryat Shmona is a northern Israeli city near the Lebanese border, known for its strategic location and frequent exposure to cross-border conflict.
  • 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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48ffb35248190a80a428686e06d87 completed April 19, 2026, 8:19 a.m.
Created at: April 10, 2026, 10:16 a.m.