Triple
T19386995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharon plain |
E484960
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Kfar Saba |
—
|
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: Kfar Saba | Statement: [Sharon plain, hasCity, Kfar Saba]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kfar Saba Context triple: [Sharon plain, hasCity, Kfar Saba]
-
A.
Kfar Saba
chosen
Kfar Saba is a city in central Israel, known as a suburban and commercial hub in the Sharon plain near Tel Aviv.
-
B.
Kfar Haim
Kfar Haim is an agricultural moshav in central Israel named in memory of Zionist leader Haim Arlosoroff.
-
C.
Kfar Shmaryahu
Kfar Shmaryahu is an affluent suburban village in central Israel known for its high standard of living and proximity to Tel Aviv.
-
D.
Kiryat Hasharon
Kiryat Hasharon is a residential neighborhood in the city of Netanya, Israel, known for its modern housing and family-oriented community.
-
E.
Kiryat Shmona
Kiryat Shmona is a northern Israeli city near the Lebanese border, known for its strategic location and frequent exposure to cross-border conflict.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b418f148190972b7b46038bc744 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.