Triple

T9662666
Position Surface form Disambiguated ID Type / Status
Subject Tel Dan E233625 entity
Predicate near P350 FINISHED
Object modern town of Kiryat Shmona E146492 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: modern town of Kiryat Shmona | Statement: [Tel Dan, near, modern town of Kiryat Shmona]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: modern town of Kiryat Shmona
Context triple: [Tel Dan, near, modern town of Kiryat Shmona]
  • A. Kiryat Shmona chosen
    Kiryat Shmona is a northern Israeli city near the Lebanese border, known for its strategic location and frequent exposure to cross-border conflict.
  • B. Kiryat Moshe
    Kiryat Moshe is a residential neighborhood in the central Israeli city of Rehovot.
  • C. Kiryat Moshe
    Kiryat Moshe is a residential neighborhood in western Jerusalem, known for its religious communities and proximity to major educational and governmental institutions.
  • D. Kiryat David
    Kiryat David is a residential neighborhood in the city of Rehovot, Israel.
  • E. Kiryat Yearim
    Kiryat Yearim is a small Israeli town with a predominantly ultra-Orthodox Jewish population, located in the hills west of Jerusalem.
  • 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_69ca848d3b6c8190ae98ea554dea58df completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9c0b7728819099473f404382b26a completed April 1, 2026, 10:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69d18a1422348190967943b0d4da8efd completed April 4, 2026, 10 p.m.
Created at: March 30, 2026, 8:14 p.m.