Triple
T20666044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiryat Yearim |
E507887
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Mevaseret Zion |
—
|
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: Mevaseret Zion | Statement: [Kiryat Yearim, locatedNear, Mevaseret Zion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mevaseret Zion Context triple: [Kiryat Yearim, locatedNear, Mevaseret Zion]
-
A.
Mevaseret Zion
chosen
Mevaseret Zion is a suburban town in central Israel located just west of Jerusalem, known primarily as a residential community for commuters to the city.
-
B.
Sha'ar Tzion
Sha'ar Tzion is the Hebrew name for the historic Zion Gate in Jerusalem’s Old City walls, a key entrance near Mount Zion.
-
C.
Beit El
Beit El is an Israeli settlement in the central West Bank that serves as a key administrative and military hub for Israeli authorities in the area.
-
D.
Ur Kasdim
Ur Kasdim is the ancient Mesopotamian city traditionally identified in the Hebrew Bible as the birthplace of the patriarch Abraham.
-
E.
Binah
Binah is the third sefirah in Kabbalistic mysticism, representing understanding, structure, and the divine feminine aspect of creation.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c2c6d48190bbfe505cf7d973f9 |
completed | April 20, 2026, 11:24 p.m. |
Created at: April 16, 2026, 11:44 a.m.