Triple
T14523442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerem Shalom |
E340709
|
entity |
| Predicate | borderCrossingHandles |
P113300
|
FINISHED |
| Object | goods to Gaza Strip |
—
|
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: goods to Gaza Strip | Statement: [Kerem Shalom, borderCrossingHandles, goods to Gaza Strip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingHandles Context triple: [Kerem Shalom, borderCrossingHandles, goods to Gaza Strip]
-
A.
borderCrossingMode
Indicates the means or method by which a border is crossed between territories or jurisdictions.
-
B.
borderCrossingArea
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
-
C.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
D.
borderCrossingRequirement
Indicates the conditions or obligations that must be met for an entity to legally or formally cross a border between jurisdictions.
-
E.
borderPostHandles
chosen
Indicates that a particular border post is responsible for managing, processing, or overseeing a specified type of traffic, activity, or operation.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea04f16f88190ba357b0f8021b46b |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.