Triple
T14572083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krayot |
E341941
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Kiryat Haim |
E350322
|
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: Kiryat Haim | Statement: [Krayot, hasPart, Kiryat Haim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kiryat Haim Context triple: [Krayot, hasPart, Kiryat Haim]
-
A.
Kiryat Haim
chosen
Kiryat Haim is a coastal neighborhood in the northern Israeli city of Haifa, known for its beachfront, residential character, and proximity to the Haifa Bay industrial and port areas.
-
B.
Kiryat Moshe
Kiryat Moshe is a residential neighborhood in the central Israeli city of Rehovot.
-
C.
Kiryat Moshe
Kiryat Moshe is a residential neighborhood in western Jerusalem, known for its religious communities and proximity to major educational and governmental institutions.
-
D.
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.
-
E.
Kiryat Ono
Kiryat Ono is a small suburban city in central Israel, located in the Tel Aviv metropolitan area.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f33b1c8190bb447788bfd28d51 |
completed | April 14, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6ec12de8819097cd83530e54f54b |
completed | May 9, 2026, 5:28 p.m. |
Created at: April 10, 2026, 1:24 a.m.