Triple

T2871387
Position Surface form Disambiguated ID Type / Status
Subject Tel Ashdod E63569 entity
Predicate locatedNear P294 FINISHED
Object Ashdod E63569 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: Ashdod | Statement: [Tel Ashdod, locatedNear, Ashdod]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashdod
Context triple: [Tel Ashdod, locatedNear, Ashdod]
  • A. Ashdod chosen
    Ashdod is a major coastal city in southern Israel that serves as an important cultural and religious hub, including for the Karaite Jewish community.
  • B. Eilat
    Eilat is Israel’s southernmost city and a major Red Sea resort and port known for its beaches, coral reefs, and tourism.
  • C. Nahariya
    Nahariya is a coastal city in northern Israel on the Mediterranean Sea, known as a resort town and gateway to nearby attractions such as Rosh HaNikra.
  • D. Ramla
    Ramla is an Israeli city historically significant as a major religious and communal center for Karaite Jews.
  • E. Qalqilya
    Qalqilya is a Palestinian city in the northwestern West Bank, known for being almost completely encircled by the Israeli West Bank barrier.
  • 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_69ab4c42fb8c8190b36e161d47c03b81 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdfe46a1c819084399a191f0dfe9c completed March 7, 2026, 8:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69b1f856ad508190a92d9e9decc68c58 completed March 11, 2026, 11:18 p.m.
Created at: March 6, 2026, 10:02 p.m.