Triple

T18971011
Position Surface form Disambiguated ID Type / Status
Subject Mateh Yehuda Regional Council E464167 entity
Predicate containsLocality P45140 FINISHED
Object Tzur Hadassah 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: Tzur Hadassah | Statement: [Mateh Yehuda Regional Council, containsLocality, Tzur Hadassah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tzur Hadassah
Context triple: [Mateh Yehuda Regional Council, containsLocality, Tzur Hadassah]
  • A. Tzur Hadassah chosen
    Tzur Hadassah is a community settlement in the Judean Hills of central Israel, located southwest of Jerusalem.
  • B. Hadassah
    Hadassah is a Hebrew female given name, traditionally associated with the biblical Queen Esther and meaning "myrtle."
  • C. Magen Avraham
    Magen Avraham is a classic and influential halachic commentary on the Shulchan Aruch, Orach Chaim, authored by Rabbi Avraham Gombiner in the 17th century.
  • D. Maoz Zion
    Maoz Zion is a former Israeli community that became part of the town of Mevaseret Zion following a municipal merger.
  • E. Yad Avshalom
    Yad Avshalom is an ancient monumental rock-cut tomb and landmark in the Kidron Valley in Jerusalem, traditionally associated with Absalom, the rebellious son of King David.
  • 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_69d8dd008af48190a97ff1c6488edf1b completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d61a8bbc8190881908a71e0f2a53 completed April 20, 2026, 7:30 a.m.
Created at: April 10, 2026, noon