Triple
T37294744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beer Sheva |
E925768
|
entity |
| Predicate | isTechnologicalHub |
P759
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Beer Sheva, isTechnologicalHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTechnologicalHub Context triple: [Beer Sheva, isTechnologicalHub, true]
-
A.
isTechnologicalHubOf
Indicates that a location serves as a central focal point for technological activity, development, or innovation for another specified area or community.
-
B.
hasTechnologicalActivity
Indicates that an entity engages in, performs, or is involved in some form of technological process, operation, or practice.
-
C.
isKeyTechnologyIn
Indicates that one technology plays a central, enabling, or foundational role within another specified context, system, or domain.
-
D.
hasAdvancedTechnologySector
chosen
Indicates that an entity possesses or includes a developed sector focused on advanced or high-tech industries, products, or services.
-
E.
hasInnovationHub
Indicates that an entity hosts, contains, or is associated with a dedicated center or facility focused on innovation activities.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.