Triple
T13467167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosh Pinna |
E311533
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Kiryat Shmona |
E146492
|
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 Shmona | Statement: [Rosh Pinna, locatedNear, Kiryat Shmona]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kiryat Shmona Context triple: [Rosh Pinna, locatedNear, Kiryat Shmona]
-
A.
Kiryat Shmona
chosen
Kiryat Shmona is a northern Israeli city near the Lebanese border, known for its strategic location and frequent exposure to cross-border conflict.
-
B.
Kiryat Haim
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.
-
C.
Kiryat Gat
Kiryat Gat is a city in south-central Israel known for its industrial zones, high-tech facilities, and location between the coastal plain and the Negev desert.
-
D.
Kiryat David
Kiryat David is a residential neighborhood in the city of Rehovot, Israel.
-
E.
Kiryat Moshe
Kiryat Moshe is a residential neighborhood in the central Israeli city of Rehovot.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf101a1081909f2aba6da47baacc |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda9009ce88190b77c8f02f38107e1 |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 9, 2026, 9:42 p.m.