Triple

T19071858
Position Surface form Disambiguated ID Type / Status
Subject Givat Shaul E466811 entity
Predicate adjacentTo P224 FINISHED
Object Kiryat Moshe 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: Kiryat Moshe | Statement: [Givat Shaul, adjacentTo, Kiryat Moshe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kiryat Moshe
Context triple: [Givat Shaul, adjacentTo, Kiryat Moshe]
  • A. Kiryat Moshe
    Kiryat Moshe is a residential neighborhood in the central Israeli city of Rehovot.
  • B. Kiryat Moshe chosen
    Kiryat Moshe is a residential neighborhood in western Jerusalem, known for its religious communities and proximity to major educational and governmental institutions.
  • C. Kiryat Haim
    Kiryat Haim is a coastal neighborhood in the northern Israeli city of Haifa, known for its beachfront, residential character, and proximity to the Haifa Bay industrial and port areas.
  • D. Kiryat Shmuel
    Kiryat Shmuel is a residential neighborhood in the Haifa Bay area of northern Israel, known as one of the Krayot suburbs of Haifa.
  • 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_69d8dd04f4488190b1121cc53ef2bfd6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e19fa6948190bdf8e8ec022e12f2 completed April 20, 2026, 8:19 a.m.
Created at: April 10, 2026, 12:04 p.m.