Triple
T25722373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modi'in Illit |
E645025
|
entity |
| Predicate | nearbyPalestinianLocalities |
P88901
|
FINISHED |
| Object | Palestinian villages in the central West Bank |
—
|
LITERAL 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: Palestinian villages in the central West Bank | Statement: [Modi'in Illit, nearbyPalestinianLocalities, Palestinian villages in the central West Bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyPalestinianLocalities Context triple: [Modi'in Illit, nearbyPalestinianLocalities, Palestinian villages in the central West Bank]
-
A.
nearbyLocalityWestBank
Indicates that one locality is geographically near another locality located in the West Bank region.
-
B.
hasNearbyArabLocality
chosen
Indicates that one entity has an Arab locality situated in close geographic proximity to it.
-
C.
nearbyIsraeliSettlement
Indicates that one entity is located close in distance to an Israeli settlement.
-
D.
distanceFromJerusalem
Indicates the spatial distance between a given location and Jerusalem.
-
E.
municipalityOnWestBank
Indicates that a municipality is located on the western bank of a specified geographic feature, such as a river or body of water.
- F. None of above.
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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 21, 2026, 10:04 p.m.