Triple
T28834317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kifl Haris |
E728135
|
entity |
| Predicate | nearbyIsraeliIndustrialZone |
P186654
|
FINISHED |
| Object | Barkan Industrial Park |
—
|
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: Barkan Industrial Park | Statement: [Kifl Haris, nearbyIsraeliIndustrialZone, Barkan Industrial Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyIsraeliIndustrialZone Context triple: [Kifl Haris, nearbyIsraeliIndustrialZone, Barkan Industrial Park]
-
A.
hasIndustrialZoneAlong
Indicates that an industrial zone is located adjacent to or extending along the length of a specified linear feature (such as a road, river, or boundary).
-
B.
nearbyIsraeliSettlement
Indicates that one entity is located close in distance to an Israeli settlement.
-
C.
nearIndustrialComplex
chosen
Indicates that one entity is located in close proximity to an industrial complex.
-
D.
connectsToIndustrialArea
Indicates that one entity has a direct link, route, or access connection to an industrial area.
-
E.
nearbyIndustrialInstallation
Indicates that one entity is located close to an industrial facility or installation.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 28, 2026, 6:38 a.m.