Triple

T19883834
Position Surface form Disambiguated ID Type / Status
Subject Rosh HaNikra E477843 entity
Predicate near P350 FINISHED
Object city of Nahariya 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: city of Nahariya | Statement: [Rosh HaNikra, near, city of Nahariya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Nahariya
Context triple: [Rosh HaNikra, near, city of Nahariya]
  • A. Nahariya chosen
    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.
  • B. Kiryat Hasharon
    Kiryat Hasharon is a residential neighborhood in the city of Netanya, Israel, known for its modern housing and family-oriented community.
  • C. Netanya
    Netanya is a coastal city in central Israel on the Mediterranean Sea, known for its beaches, tourism, and role as a regional economic center.
  • D. Kiryat Ono
    Kiryat Ono is a small suburban city in central Israel, located in the Tel Aviv metropolitan area.
  • E. Hadera
    Hadera is a coastal city in northern Israel known for its power station, beaches, and location between Tel Aviv and Haifa.
  • 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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6590870908190a18b545f0ff0ccd6 completed April 20, 2026, 4:49 p.m.
Created at: April 10, 2026, 1:52 p.m.